Fri Feb 12 16:37:58 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 ]
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. -- Alvaro Herrera Vendo parcela en Valdivia: http://alvherre.cl/caboblanco "The Gord often wonders why people threaten never to come back after they've been told never to return" (www.actsofgord.com)
- 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