Re: Postgres-R: primary key patches

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Markus Wanner <markus(at)bluegap(dot)ch>
Cc: chris <cbbrowne(at)ca(dot)afilias(dot)info>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgres-R: primary key patches
Date: 2008-07-22 17:15:49
Message-ID: 20080722171549.GB7260@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Markus Wanner wrote:

>> Ideally, we'd take an outage and add the primary key. But suppose we
>> can't afford to do so?
>
> You are assuming that one doesn't need to take an outage to start
> replication in the first place. As Postgres-R comes with system catalog
> changes, that's not the case. You will at least need to restart the
> postmaster, without some sort of system catalog upgrading (which doesn't
> currently exists) you even need a full dump/restore cycle.

Hey, for Replicator I wrote a bootstrapping system for "catalog
upgrading" -- it starts a special "bootstrap mode" and allows creating
new catalogs, their indexes, and a bunch of functions. Afterwards
everything is considered "internal".

It's quite hackish but it works ...

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message chris 2008-07-22 17:16:04 Slony-I playing with system catalog
Previous Message Zdenek Kotala 2008-07-22 17:03:26 Re: [WIP] collation support revisited (phase 1)