Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] problems with dropped columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Damjan Pipan <damjan(dot)pipan(at)siol(dot)net>, pgsql-general(at)postgresql(dot)org,Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] problems with dropped columns
Date: 2003-03-06 06:18:41
Message-ID: 13092.1046931521@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Joe Conway <mail(at)joeconway(dot)com> writes:
> Taking it a bit further...

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.

The former problem is just a small matter of programming in plpgsql;
I'm not sure what the best way to do it is, but it's clearly just
plpgsql's issue.  The latter problem calls for a ton of infrastructure
that we haven't got :-(

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2003-03-06 06:36:02
Subject: Re: Alpha-2 of contrib/tsearch
Previous:From: Dennis GearonDate: 2003-03-06 06:15:54
Subject: Re: My contract has been renewed

pgsql-general by date

Next:From: Oleg BartunovDate: 2003-03-06 06:36:02
Subject: Re: Alpha-2 of contrib/tsearch
Previous:From: Dennis GearonDate: 2003-03-06 06:15:54
Subject: Re: My contract has been renewed

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group