From: Scott Ribe <scott_ribe@elevated-dev.com>
To: AL-Temimi, Muthana <muthana.al-temimi@tu-harburg.hamburg.de>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Latest checkpoint's NextOID
Date: Thu, 25 Sep 2014 07:53:00 -0600
Message-ID: <8D4BB505-C111-446E-81F9-91EA382E9371@elevated-dev.com> (raw)
In-Reply-To: <CA+U5nMLv4p1Mh4n=YtKznrhHz+yWPWw4yQo6qFKj9YJwBw3gwA@mail.gmail.com>
References: <24F2E095E199B041912675E4E3BBA0117C7AFE9F@WEXCPPA018.fhhnet.stadt.hamburg.de>
<CA+U5nMLv4p1Mh4n=YtKznrhHz+yWPWw4yQo6qFKj9YJwBw3gwA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On 25 September 2014 11:12, AL-Temimi, Muthana
<muthana.al-temimi@tu-harburg.hamburg.de> wrote:
> i’m using 9.1 PostgreSQL and looking for a function to write WAL to table in
> order to save all the data into database and to make a recovery on the 2nd
> DB Server.
>
>
>
> The idea is to help recovery on other server and get the same OID on the 2nd
> Server and that’s by using the Latest checkpoint's NextOID from the first
> Server.
Why not use WAL-shipping or streaming replication the normal way?
You do realize that everything that goes into tables goes into the WAL, so you write WAL into a table, the table gets logged to WAL, and then that WAL... That's just not going to work, unless you use an unlogged table, in which case you have a replication/recovery mechanism which is inherently unreliable, which is pretty worthless. So the whole idea seems to be unrealistic.
Now, if you want to log changes to tables into a table, that's doable via triggers, usually for audit purposes, but it can be used to keep replicas in synch. It's just that it's hard to imagine what you'd do that Slony-I doesn't already do, assuming you even need its features as opposed to streaming replication.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, muthana.al-temimi@tu-harburg.hamburg.de
Subject: Re: Latest checkpoint's NextOID
In-Reply-To: <8D4BB505-C111-446E-81F9-91EA382E9371@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox