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: 2006-08-29 02:18:14
Message-ID: 22860.1156817894@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc pgsql-patches

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-08-29 02:22:33 Re: [HACKERS] [PATCHES] log_statement output for protocol
Previous Message Bruce Momjian 2006-08-29 02:09:51 Re: [HACKERS] Performance testing of COPY (SELECT)

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2006-08-29 02:22:33 Re: [HACKERS] [PATCHES] log_statement output for protocol
Previous Message Bruce Momjian 2006-08-29 02:08:33 Re: [HACKERS] [PATCHES] log_statement output for protocol

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-08-29 02:22:33 Re: [HACKERS] [PATCHES] log_statement output for protocol
Previous Message Bruce Momjian 2006-08-29 02:09:51 Re: [HACKERS] Performance testing of COPY (SELECT)