Tue Feb 16 08:37:47 PST 2010
- Previous message: [Slony1-general] [HACKERS] logtrigger issue in PostgreSQL HEAD
- Next message: [Slony1-general] [HACKERS] logtrigger issue in PostgreSQL HEAD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alvaro Herrera <alvherre at alvh.no-ip.org> writes: > Christopher Browne wrote: > >> That's not "line 487" as I see it... The full function call was... >> >> log_status = DatumGetInt32(SPI_getbinval(SPI_tuptable->vals[0], >> SPI_tuptable->tupdesc, 1, NULL)); > > I think the problem may be that you're no longer able to pass a NULL > as fourth argument here. There are several calls to SPI_getbinval(), just one of which fails in this manner. Changing that one instance allows my regression test to succeed, so I reckon you have identified the problem correctly. I'll do a bit more testing before committing, but that looks mighty promising. -- let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;; Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-general] [HACKERS] logtrigger issue in PostgreSQL HEAD
- Next message: [Slony1-general] [HACKERS] logtrigger issue in PostgreSQL HEAD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list