| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Damjan Pipan <damjan(dot)pipan(at)siol(dot)net>, <pgsql-general(at)postgresql(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] problems with dropped columns |
| Date: | 2003-03-08 04:09:01 |
| Message-ID: | 20030308120830.H22143-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> > There are (at least) two distinct problems involved here. One is
> > getting plpgsql to deal correctly with rowtypes that include dropped
> > columns. The other is getting it to react when someone alters a table
> > whose rowtype is relied on by already-compiled functions.
I'm working on this one...I don't know all the dependencies of things off
the top of my head, so it's a little bit painstakign...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Christian Imbeault | 2003-03-08 04:33:44 | Re: Unexpected parse behaviour for date to timestamp |
| Previous Message | Richard Welty | 2003-03-08 02:57:13 | Re: Replacing rpm installation with tarball |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-08 04:24:15 | Re: Precompile SQL functions |
| Previous Message | Bruce Momjian | 2003-03-08 03:54:29 | Precompile SQL functions |