Re: Poor plan choice in prepared statement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: david(at)lang(dot)hm
Cc: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Scott Carey <scott(at)richrelevance(dot)com>, bricklen <bricklen(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Poor plan choice in prepared statement
Date: 2009-01-01 20:24:12
Message-ID: 10355.1230841452@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

david(at)lang(dot)hm writes:
> the poster who started this thread had a query where the parsing phase
> took significantly longer than the planning stage.

That was an anecdote utterly unsupported by evidence.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message david 2009-01-01 20:24:52 Re: Poor plan choice in prepared statement
Previous Message Guillaume Smet 2009-01-01 19:29:43 Re: Poor plan choice in prepared statement