Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XX9U2-0007h9-Nz for pgsql-admin@arkaria.postgresql.org; Thu, 25 Sep 2014 13:53:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XX9U2-0007U0-0w for pgsql-admin@arkaria.postgresql.org; Thu, 25 Sep 2014 13:53:22 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XX9Tz-0007Ov-S8 for pgsql-admin@postgresql.org; Thu, 25 Sep 2014 13:53:20 +0000 Received: from mailout.easymail.ca ([64.68.201.169]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XX9Tw-0004v6-2D for pgsql-admin@postgresql.org; Thu, 25 Sep 2014 13:53:17 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 4DEC6E039; Thu, 25 Sep 2014 09:53:14 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -4.376 X-Spam-Level: X-Spam-Status: No, score=-4.376 required=5 tests=[ALL_TRUSTED=-1.8, AWL=0.023, BAYES_00=-2.599] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5tEl7SYt8c4; Thu, 25 Sep 2014 09:53:13 -0400 (EDT) Received: from [192.168.2.16] (unknown [8.39.228.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 03728E024; Thu, 25 Sep 2014 09:53:12 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Latest checkpoint's NextOID From: Scott Ribe In-Reply-To: Date: Thu, 25 Sep 2014 07:53:00 -0600 Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <8D4BB505-C111-446E-81F9-91EA382E9371@elevated-dev.com> References: <24F2E095E199B041912675E4E3BBA0117C7AFE9F@WEXCPPA018.fhhnet.stadt.hamburg.de> To: "AL-Temimi, Muthana" X-Mailer: Apple Mail (2.1878.6) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 25 September 2014 11:12, AL-Temimi, Muthana wrote: > i=92m using 9.1 PostgreSQL and looking for a function to write WAL to tab= le in > order to save all the data into database and to make a recovery on the 2nd > DB Server. >=20 >=20 >=20 > The idea is to help recovery on other server and get the same OID on the = 2nd > Server and that=92s by using the Latest checkpoint's NextOID from the fir= st > 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 whi= ch case you have a replication/recovery mechanism which is inherently unrel= iable, 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 t= riggers, 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 does= n't already do, assuming you even need its features as opposed to streaming= replication. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin