Re: Attempting upgrade path; is this possible? - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Attempting upgrade path; is this possible?
Date
Msg-id 20060223002217.GO86022@pervasive.com
Whole thread Raw
In response to Re: Attempting upgrade path; is this possible?  (Hannu Krosing <hannu@skype.net>)
List pgsql-hackers
On Thu, Feb 23, 2006 at 12:51:29AM +0200, Hannu Krosing wrote:
> The requirement for (candidate) primary key's may still be prohibiting,
> as currently creating an index on large table locks that table for
> writes for the duration of create index.

Plus, if the tables already have OIDs, you *might* be able to create a
unique index on those (watch out for OID rollover, though) and tell
slony to use that (actually, one of the perl tools should pick it up
automagically).

Or, like Hannu suggests, just let slony create the keys for you. You can
always drop them later. Actually, I believe Slony will drop them for you
if you drop the node.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Pgfoundry and gborg: shut one down
Next
From: Alvaro Herrera
Date:
Subject: Re: PostgreSQL unit tests