Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [HACKERS] [PATCHES] log_statement output for protocol
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Bruce Momjian <bruce(at)momjian(dot)us>
- Cc: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, 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: Mon, 28 Aug 2006 22:18:14 -0400
Bruce Momjian <bruce(at)momjian(dot)us> writes: > Yes, I do. I have applied the attached patch to fix this issue and > several others. The fix was to save the bind parameters in the portal, > and display those in the executor output, if available. I have a feeling you just blew away the 4% savings in psql I've spent the evening on. What's the overhead of this patch? regards, tom lane
- Follow-Ups:
- Re: [HACKERS] [PATCHES] log_statement output for protocol
- From: Bruce Momjian
- Re: [HACKERS] [PATCHES] log_statement output for protocol
- References:
- Re: [HACKERS] [PATCHES] log_statement output for protocol
- From: Bruce Momjian
- Re: [HACKERS] [PATCHES] log_statement output for protocol
- Prev by Date: Re: [HACKERS] [PATCHES] log_statement output for protocol
- 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: Re: [HACKERS] [PATCHES] log_statement output for protocol
- Indexes: