I know there are some limitations abut it:
- copy statements cannot be executed,
- the use of now() function
- even database restore scripts I don't want to be replicated
but these are not a problem for me because I don't use them in the application...
--- On Thu, 11/27/08, Csaba Nagy <nagy@ecircle-ag.com> wrote:
> From: Csaba Nagy <nagy@ecircle-ag.com>
> Subject: Re: [GENERAL] Using postgres.log file for replication
> To: ioanasoftware@yahoo.ca
> Cc: "PostgreSQL General" <pgsql-general@postgresql.org>
> Received: Thursday, November 27, 2008, 12:24 PM
> On Thu, 2008-11-27 at 09:20 -0800, Ioana Danes wrote:
> > I've been wondering if anybody tried to use the
> postgresql csv log file to replicate sql statements.
> > I've been looking into it in the past days and
> after a brief testing it doesn't look bad at all...
>
> Try to execute something like:
>
> UPDATE some_table SET some_timestamp_field = now();
>
> The replica is now different than the master :-)
>
> Cheers,
> Csaba.
>
>
>
> --
> Sent via pgsql-general mailing list
> (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
__________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at
http://ca.toolbar.yahoo.com.