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