From: | Ioana Danes <ioanasoftware(at)yahoo(dot)ca> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Csaba Nagy <nagy(at)ecircle-ag(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using postgres.log file for replication |
Date: | 2008-11-27 18:33:13 |
Message-ID: | 32182.65392.qm@web45116.mail.sp1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the tip Scott but am looking for an asynchronous replication that does not interfere with the performance of the application. Also I don't necessary need the latest changes to be applied right away. Even a day difference is enough...
Thanks a lot,
Ioana
--- On Thu, 11/27/08, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
> Subject: Re: [GENERAL] Using postgres.log file for replication
> To: ioanasoftware(at)yahoo(dot)ca
> Cc: "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org>
> Received: Thursday, November 27, 2008, 12:34 PM
> If you want the same thing in real time look into pgpool II
>
> On Thu, Nov 27, 2008 at 10:28 AM, Ioana Danes
> <ioanasoftware(at)yahoo(dot)ca> wrote:
> > 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(at)ecircle-ag(dot)com> wrote:
> >
> >> From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
> >> Subject: Re: [GENERAL] Using postgres.log file for
> replication
> >> To: ioanasoftware(at)yahoo(dot)ca
> >> Cc: "PostgreSQL General"
> <pgsql-general(at)postgresql(dot)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(at)postgresql(dot)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.
> >
> >
> > --
> > 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
> >
>
>
>
> --
> When fascism comes to America, it will be draped in a flag
> and
> carrying a cross - Sinclair Lewis
>
> --
> 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
__________________________________________________________________
Instant Messaging, free SMS, sharing photos and more... Try the new Yahoo! Canada Messenger at http://ca.beta.messenger.yahoo.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-11-27 18:53:37 | Re: Using postgres.log file for replication |
Previous Message | Andrus | 2008-11-27 17:44:05 | Increase column width only if it is different |