| From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeroen Vermeulen <jtv(at)xs4all(dot)nl>, Greg Stark <gsstark(at)mit(dot)edu>, Bart Samwel <bart(at)samwel(dot)tk>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Avoiding bad prepared-statement plans. |
| Date: | 2010-02-26 04:46:20 |
| Message-ID: | 34d269d41002252046n2b117436u845a25f892c02629@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 25, 2010 at 21:28, Alex Hunsaker <badalex(at)gmail(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-26 04:47:39 | Re: A thought on Index Organized Tables |
| Previous Message | Gokulakannan Somasundaram | 2010-02-26 04:33:35 | Re: A thought on Index Organized Tables |