Re: A few user-level questions on Streaming Replication and pg_upgrade

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A few user-level questions on Streaming Replication and pg_upgrade
Date: 2011-07-20 20:02:56
Message-ID: CA+TgmoYaeb6JL6DjOpHkAOXhOQyC9qoz5VVrU+4-1DNDG24PSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Wed, Jul 20, 2011 at 3:29 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Haas wrote:
>> On Wed, Jul 20, 2011 at 2:53 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> >> I am assuming that's a "yes" to both the directions: older -> newer , and
>> >> newer -> older minor releases.
>> >
>> > Yes, I believe both directions would work unless we mentioned it the
>> > release notes, in which cases it might not work, or might work older to
>> > newer but newer to older.
>>
>> I don't see how this would get broken in a minor release.  We'd have
>> to change the WAL format or the tuple format, which is definitely not
>> minor release material.
>
> If there was a bug in the xlog stream content we might not be able to
> fix it without breaking compatibility.  Rare, but possible.

OK, fair enough. But I think the likelihood is extremely low.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2011-07-20 20:47:50 Re: A few user-level questions on Streaming Replication and pg_upgrade
Previous Message Bruce Momjian 2011-07-20 19:29:07 Re: A few user-level questions on Streaming Replication and pg_upgrade

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-07-20 20:06:33 Re: Another issue with invalid XML values
Previous Message Kevin Grittner 2011-07-20 19:33:56 Re: WIP fix proposal for bug #6123