From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hannu Krosing <hannu(at)krosing(dot)net>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Stephen Denne <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Core team statement on replication in PostgreSQL |
Date: | 2008-06-04 16:16:40 |
Message-ID: | 1212596200.4148.123.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Wed, 2008-06-04 at 11:37 -0400, Tom Lane wrote:
> This thread is getting out of hand, actually.
Agreed. We should start new threads for specific things. Please.
> However, since by definition pg_control doesn't change in a minor
> upgrade, there isn't any easy way to enforce a rule like "slaves must be
> same or newer minor version as the master". I'm not sure that we
> actually *want* to enforce such a rule, though.
Definitely don't want to prevent minor version mismatches. We want to be
able to upgrade a standby, have it catch up with the master then
switchover to the new version. Otherwise we'd have to take whole
replicated system down to do minor upgrades/backouts. Ugh!
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-06-04 16:52:09 | Re: Brochures for upcoming shows (was Re: Live CDs for upcoming shows) |
Previous Message | Mike Ellsworth | 2008-06-04 16:10:51 | Re: Brochures for upcoming shows (was Re: Live CDs for upcoming shows) |
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2008-06-04 17:00:13 | Re: Overhauling GUCS |
Previous Message | Tom Lane | 2008-06-04 16:06:44 | Re: keyword list/ecpg |