Re: Planning incompatibilities for Postgres 10.0

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Planning incompatibilities for Postgres 10.0
Date: 2013-05-26 13:18:11
Message-ID: 20130526131811.GA32039@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 26, 2013 at 10:53:37AM +0100, Simon Riggs wrote:
> > I consider this thread to be not thought-through, obviously.
>
> My proposal has had lots of serious consideration, but that is not the
> topic of this thread.
>
> The title of the thread is a general one, with a clear objective.
>
> I'm looking for a way forwards that allows us to introduce the changes
> that many have proposed and which regrettably result in
> incompatibilities. If we have no plan I think its likely it will never
> happen and it is currently blocking useful change.
>
> Please explain what you consider to be a better plan, so we can judge
> all proposals together.

I agree with the idea of using logical replication as a way to do
pg_upgrade version-breaking releases. What I don't know is what
incompatible changes are pending that would require this.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-05-26 13:22:45 Re: Planning incompatibilities for Postgres 10.0
Previous Message Hannu Krosing 2013-05-26 12:15:14 Re: getting rid of freezing