Re: Log all queries before migration ?

On Wed, Aug 3, 2016 at 10:10 AM, Charles Clavadetscher <
clavadetscher(at)swisspug(dot)org> wrote:

> Hello
>
> > -----Original Message-----
> > From: pgsql-general-owner(at)postgresql(dot)org [mailto:
> pgsql-general-owner(at)postgresql(dot)org] On Behalf Of ben.play
> > Sent: Mittwoch, 3. August 2016 15:29
> > To: pgsql-general(at)postgresql(dot)org
> > Subject: Re: [GENERAL] Log all queries before migration ?
> >
> > Hi guys,
> >
> > In fact, I would like to copy a table and then, when everything is
> finish, execute all inserts and updates since the
> > beginning of the copy.
> >
> > The biggest problem with the log at this time it's the query.
> > All my queries are not runnable.
>
> This may help you?
>
> http://laurenz.github.io/pgreplay/
>
> Regards
> Charles
>
> >
> > When I log, I see this kind of queries :
> > "duration: 0.046 ms parse <unnamed>: UPDATE user SET money = money + $1
> WHERE id = $2"
> >
> > But I would like to have only : "UPDATE user SET money = money + 100
> WHERE id = 1281012"
> >
> > This is our postgresql.conf :
> > log_destination = 'csvlog'
> > logging_collector = on
> > log_min_duration_statement = 0
> > log_statement = mod
> > log_directory = '/media/hdd/log_queries'
> > log_filename='log_insert.log'
> > log_file_mode = 0600
> > log_error_verbosity = verbose
> >
> >
> > What do we have to change ?
> >
> > Thank you a lot for your help !
> >
> >
> >
> > --
> > View this message in context:
> http://postgresql.nabble.com/Log-all-queries-before-migration-tp5913922p5914599.html
> > Sent from the PostgreSQL - general mailing list archive at Nabble.com.
> >
> >
> > --
> > Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org) To
> make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-general
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

T

*here is no way to record queries and shut down the server at the same
time.That's like saying I want to shut off my car engine but keep driving.I
believe you are looking at the wrong solution. The best way to migrate and
keep all transactions is to use Slony
replication.http://slony.info/adminguide/2.2/doc/adminguide/slony.pdf
<http://slony.info/adminguide/2.2/doc/adminguide/slony.pdf>http://slony.info/downloads/2.2/
<http://slony.info/downloads/2.2/>You can start the migration to the new
server and when it's finished, you simply failover to the slave and
redirect the url to it. *

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.