| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Rakesh Kumar <rakeshkumar464a3(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Uber migrated from Postgres to MySQL |
| Date: | 2016-07-27 16:54:30 |
| Message-ID: | 20160727165430.GC27332@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 27, 2016 at 12:51:40PM -0400, Rakesh Kumar wrote:
> On Wed, Jul 27, 2016 at 12:47 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> > Yes. I was saying I don't know how to improve pg_upgrade to address it.
>
> This problem is there even in oracle/db2/sqlserver. None of them allow
> rollback to the lower version
> unless it is a minor version upgrade. Major version upgrade almost
> definitely involves change in transaction log
> (WAL) structure and hence no rollback.
Oh, good to know.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2016-07-27 16:54:44 | Re: Uber migrated from Postgres to MySQL |
| Previous Message | Rakesh Kumar | 2016-07-27 16:51:40 | Re: Uber migrated from Postgres to MySQL |