On Wed, Feb 15, 2012 at 12:58 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> As per http://archives.postgresql.org/pgsql-general/2012-02/msg00304.php
> there is no switch case in shdepReassignOwned for foreign data wrappers.
> The obvious short-term answer (and probably the only back-patchable one)
> is to add a case for that object type. But after all the refactoring
> that's been done in the general area of this type of command, I'm a bit
> surprised that shdepReassignOwned still looks like this. Can't we merge
> this knowledge into someplace where it doesn't have to be maintained
Hmm. I guess we could add function pointers to the ObjectProperty
array in objectaddress.c. Then we could just search the array for the
catalog ID and call the associated function through the function
pointer, rather than having a switch in shdepReassignOwned(). Since
anyone adding a new object type ought to be looking at objectaddress.c
anyway, that would be one less place for people to forget to update.
However, I'm not 100% sure that's an improvement. Switches by object
type are probably not going to go away...
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-02-20 15:37:45|
|Subject: Re: REASSIGN OWNED lacks support for FDWs |
|Previous:||From: Tom Lane||Date: 2012-02-20 15:22:50|
|Subject: Re: Incorrect behaviour when using a GiST index on points |