| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jignesh Shah <J(dot)K(dot)Shah(at)Sun(dot)COM> |
| Cc: | pgsql-performance(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Performance of Parser? |
| Date: | 2007-01-14 00:24:28 |
| Message-ID: | 28391.1168734268@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Jignesh Shah <J(dot)K(dot)Shah(at)Sun(dot)COM> writes:
> The appserver is basically using bunch of prepared statements that the
> server should be executing directly without doing the parsing again.
Better have another look at that theory, because you're clearly spending
a lot of time in parsing (operator resolution to be specific). I think
your client code is failing to re-use prepared statements the way you
think it is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-01-14 00:48:14 | Re: Performance of Parser? |
| Previous Message | Tom Lane | 2007-01-14 00:14:52 | Re: Memory context in exception handler |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-01-14 00:48:14 | Re: Performance of Parser? |
| Previous Message | Jignesh Shah | 2007-01-13 23:38:24 | Performance of Parser? |