Re: Removing pg_migrator limitations - Mailing list pgsql-hackers

From decibel
Subject Re: Removing pg_migrator limitations
Date
Msg-id 3EE3F867-3646-47DC-8CD5-22FAE918D0FB@decibel.org
Whole thread Raw
In response to Re: Removing pg_migrator limitations  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Removing pg_migrator limitations
List pgsql-hackers
On Dec 19, 2009, at 9:52 PM, Robert Haas wrote:
> On Sat, Dec 19, 2009 at 10:46 PM, Bruce Momjian <bruce@momjian.us> wrote:
>> Tom Lane wrote:
>>>> Bruce Momjian wrote:
>>>>> Seems I need some help here.
>>>
>>> I'm willing to work on this --- it doesn't look particularly fun but
>>> we really need it.
>>
>> You don't know fun until you have tried to stack hack upon hack and
>> still create a reliable migration system.  :-(
>
> They say that people who love sausage and respect the law should never
> watch either one being made, and I have to say I'm coming to feel that
> way about in-place upgrade, too.

Perhaps we should be ordering bacon instead of sausage...

Is there some reason why OIDs were used for ENUM instead of a general sequence? Were we worried about people screwing
withthe sequence? 

A sequences would presumably eliminate all these issues. Even if we wanted to disallow user access to the sequence,
havingsomething that's not competing with all the other uses of OID would presumably make this a lot simpler. 
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net




pgsql-hackers by date:

Previous
From: decibel
Date:
Subject: Re: Streaming Rep - 2-phase backups and reducing time to full replication
Next
From: decibel
Date:
Subject: Re: Re: About "Allow VIEW/RULE recompilation when the underlying tables change"