Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [HACKERS] [PATCHES] log_statement output for protocol
- From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
- To: "Bruce Momjian" <bruce(at)momjian(dot)us>
- Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Oliver Jowett" <oliver(at)opencloud(dot)com>, "Dave Cramer" <pg(at)fastcrypt(dot)com>, "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, "Postgres JDBC" <pgsql-jdbc(at)postgresql(dot)org>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
- Subject: Re: [HACKERS] [PATCHES] log_statement output for protocol
- Date: Tue, 29 Aug 2006 13:22:58 +0200
Bruce, I made a few tests here and the backend terminates with a SIG11 when a parameter has the NULL value (it was logged as "(null)" before). I suspect the new code broke something (perhaps it's due to the escaping). -- Guillaume
- References:
- Re: [HACKERS] [PATCHES] log_statement output for protocol
- From: Bruce Momjian
- Re: [HACKERS] [PATCHES] log_statement output for protocol
- Prev by Date: outOfMemoryError
- Next by Date: Re: [HACKERS] [PATCHES] log_statement output for protocol
- Previous by thread: Re: [HACKERS] [PATCHES] log_statement output for protocol
- Next by thread: outOfMemoryError
- Indexes: