Re: No subject

From: Richard Huxton <dev(at)archonet(dot)com>
To: nando(at)freemail(dot)gr
Cc: pgsql-general(at)postgresql(dot)org, otsakir(at)gmail(dot)com
Subject: Re: No subject
Date: 2006-11-06 08:36:04
Message-ID: 454EF3F4.9030608@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tsakiridis Orestis wrote:
> Hi,
>
> I'm looking for a way to monitor all the queries that are executed by
> the server and to be able, by using these queries, to reproduce the
> data in all databases.

Beware - query shipping runs into problems with
DELETE FROM my_table WHERE ts < now()

> The idea is to periodicaly (e.g. every two
> minutes) store the newly executed queries in a sort of wal segment
> file. I first tried to figure this out by monitoring the data in the
> wal file that is currently being updated (in the directory
> .../pg_xlogs). I hoped that it would be blank (filled with zeroes)
> from the last wal info inserted up to the end of the file. That was
> not the case. The wal files are recycled and the new wal info is
> written over the old one.

If the current PITR isn't good enough for you:
http://www.postgresql.org/docs/8.1/static/backup.html

Check that the changes in 8.2 beta aren't helpful
http://www.postgresql.org/developer/beta

> Finally, I also thought about placing a trigger in every table's
> update but this is far too complicated and cannot be applied to
> already functional database applications.

Have you looked at slony?
http://gborg.postgresql.org/project/slony1/projdisplay.php

The word you want to search on for all this is "replication".

--
Richard Huxton
Archonet Ltd

In response to

  • No subject at 2006-11-06 07:53:45 from Tsakiridis Orestis

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2006-11-06 08:41:09 Re: Header meaning for pg_dump
Previous Message Richard Huxton 2006-11-06 08:30:48 Re: select result / functions from another database in