Re: Back-out V10 upgrade but keep new data

In theory it could work, but I think that's error prone, you'd need to parse statements and their parameters, and concurrency could play a role in data consistency depending on your transaction isolation levels, etc. If any of the statements fails for whatever reason, you can't just skip them if you are to guarantee consistency, pgpool works by doing what you suggest but all PG versions must be the same. 

What's your average dml transaction volume ?

On Wed, Jan 23, 2019 at 1:51 PM Rossi, Maria <maria.rossi@jackson.com> wrote:

Also,   if we set the log_statement = ‘all’, can I extract those statements and run against the restored V9.3 database?

What do you think?  Would that work?

 

Thanks.

 

Maria

 

 

From: Rene Romero Benavides <rene.romero.b@gmail.com>
Sent: Wednesday, January 23, 2019 2:12 PM
To: Rossi, Maria <maria.rossi@jackson.com>
Cc: pgsql-sql@lists.postgresql.org
Subject: Re: Back-out V10 upgrade but keep new data

 

EXTERNAL EMAIL

Check this out for CDC, haven't used it myself but I'm looking forward. 

https://debezium.io/

 

On Wed, Jan 23, 2019 at 1:06 PM Rossi, Maria <maria.rossi@jackson.com> wrote:

Hi,

 

If I upgrade Postgres from V9.3 to V10, then need to roll-back to V9.3 after data been entered, is there a way for me to save the new data so that I can re-apply it to the V9.3?  After I restore my V9.3 backup, can I simply replay the V10 log unto V9.3?  What are my options, if any?

 

Thanks.

Maria 

 

 

--

El genio es 1% inspiración y 99% transpiración.
Thomas Alva Edison
http://pglearn.blogspot.mx/

 

--

El genio es 1% inspiración y 99% transpiración.
Thomas Alva Edison
http://pglearn.blogspot.mx/