Horton
Menu

Re: Avoiding bad prepared-statement plans.

Alex Hunsaker <badalex@gmail.com>

View thread
From: Alex Hunsaker <badalex@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Jeroen Vermeulen <jtv@xs4all.nl>, Greg Stark <gsstark@mit.edu>, Bart Samwel <bart@samwel.tk>, Pavel Stehule <pavel.stehule@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-02-26T04:46:20Z
Lists: pgsql-hackers 
On Thu, Feb 25, 2010 at 21:28, Alex Hunsaker <badalex@gmail.com> wrote:
> Not to mention you can already do this more or less client side with a
> nice driver.
> [ uninformed noise ... ]

I did seem to miss the part where everyone thinks this is a crock...
But I don't remember seeing numbers on parse time or how much
bandwidth this would potentially save.  People seem to think it would
be a big savings for just those 2 reasons?  Or did I miss some other
benefit?