| From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
|---|---|
| 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-28 14:38:49 |
| Message-ID: | 58c91ec9-e3d8-239e-79a0-ea15f19d23cb@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 27.07.2016 19:51, 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.
>
>
Sorry, what? You can rollback to previous version of software what you had.
https://docs.oracle.com/cd/E11882_01/server.112/e23633/downgrade.htm#UPGRD007
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moreno Andreo | 2016-07-28 14:41:28 | Re: WAL directory size calculation |
| Previous Message | Markus Kolb | 2016-07-28 14:29:36 | Multiple NOTIFY is ignored |