Re: Using the extract() function in plpgsql

From: Kristis Makris <kristis(dot)makris(at)datasoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Huxton <dev(at)archonet(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Using the extract() function in plpgsql
Date: 2001-06-27 20:51:07
Message-ID: 200106272051.f5RKpEa87653@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-sql

On 27 Jun 2001 16:04:28 -0400, Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
> > 2. bad oid reference - even if we did recreate the table, the reference
> > to it is compiled in after the first run. Don't see a way around this one.
>
> You could work around that by making all the queries referencing the
> temp table be built up as strings and EXECUTE'd, rather than just
> writing them in-line in the plpgsql code. Pretty grotty but it might
> serve for now. Eventually plpgsql needs to have a way to discard
> query plans that have been obsoleted by DDL changes.
>
> regards, tom lane

Good point, but this approach might not be able to handle all the
queries required to be executed. In particular the EXECUTE of SELECT ...
INTO is not implemented yet, as of Postgres 7.1.2. Any thoughts on when
this feature will be implemented? 7.1.x ? 7.x ?

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Harry Yau 2001-06-28 06:57:37 Transaction Log
Previous Message Tom Lane 2001-06-27 20:04:28 Re: Using the extract() function in plpgsql

Browse pgsql-sql by date

  From Date Subject
Next Message kakerjak 2001-06-27 21:09:14 Subquery error. Help please!!
Previous Message Tom Lane 2001-06-27 20:04:28 Re: Using the extract() function in plpgsql