Postgres Pro
Downloads
Home   >   mailing lists

Re: Adding nextval() to a select caused hang/very slow execution - Mailing list pgsql-performance

From Tom Lane
Subject Re: Adding nextval() to a select caused hang/very slow execution
Date
Msg-id 1322417.1604524589@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding nextval() to a select caused hang/very slow execution  (Eric Raskin <eraskin@paslists.com>)
Responses Re: Adding nextval() to a select caused hang/very slow execution  (Eric Raskin <eraskin@paslists.com>)
List pgsql-performance
Tree view 
Eric Raskin <eraskin@paslists.com> writes:
> So, things get even weirder.   When I execute each individual select
> statement I am generating from a psql prompt, they all finish very
> quickly.
> If I execute them inside a pl/pgsql block, the second one hangs.
> Is there something about execution inside a pl/pgsql block that is
> different from the psql command line?

Generic vs specific plan, perhaps?  Are you passing any parameter
values in from plpgql variables?

IIRC, you could force the matter by using EXECUTE, though it's
somewhat more notationally tedious.  In late-model PG versions,
plan_cache_mode could help you too.

            regards, tom lane

pgsql-performance by date:

Previous
From: Eric Raskin
Date:
Subject: Re: Adding nextval() to a select caused hang/very slow execution
Next
From: Koteswara Rao Daliparthi
Date:
Subject: Low cost query - running longer