X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id AF92011F65DC for ; Fri, 21 Apr 2006 01:18:31 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.286 X-Spam-Level: X-Spam-Status: No, score=0.286 required=5 tests=[AWL=0.285, HTML_MESSAGE=0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id Jnj3qfWIXM-I for ; Fri, 21 Apr 2006 01:18:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from stash.illumen.com (unknown [64.207.29.137]) by postgresql.org (Postfix) with ESMTP id BD23F11F65C6 for ; Fri, 21 Apr 2006 01:18:27 -0300 (ADT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C664FA.A36A60C3" Subject: Re: Howto: Using PITR recovery for standby replication X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 20 Apr 2006 22:18:27 -0600 Message-ID: <8511B4970E0D124898E973DF496F9B4357E0F7@stash.stackdump.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Howto: Using PITR recovery for standby replication Thread-Index: AcZk+G9MeVaNhl3WRe+uyvF89aTAXAAATD62 References: <443F9BF3.4060101@laposte.net> <1145028323.5597.1.camel@localhost.localdomain> <443FDF05.4060600@laposte.net> <20060421014243.GR49405@pervasive.com> <8511B4970E0D124898E973DF496F9B4357E0F4@stash.stackdump.local> <2764.1145588998@sss.pgh.pa.us> <8511B4970E0D124898E973DF496F9B4357E0F5@stash.stackdump.local> <20060421040224.GM5426@surnet.cl> From: "Benjamin Krajmalnik" To: "Alvaro Herrera" Cc: "Tom Lane" , X-Archive-Number: 200604/218 X-Sequence-Number: 21387 This is a multi-part message in MIME format. ------_=_NextPart_001_01C664FA.A36A60C3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Alvaro, =20 I am a newbie, so I essentially invoked pg_dump from with pgAdmin3, with = the defaults (including large objects). This is the command being issued: =20 .C:\Program Files\PostgreSQL\8.1\bin\pg_dump.exe -i -h 172.20.0.32 -p = 5432 -U postgres -F c -b -v -f "C:\Documents and = Settings\administrator.MS\testbk.backup" events =20 What I assumed was happening (and I may have very well been wrong) was = that I was getting a consistent backup of the object at the time that it = was processed, but not the database as a whole. =20 ________________________________ From: Alvaro Herrera [mailto:alvherre@commandprompt.com] Sent: Thu 4/20/2006 10:02 PM To: Benjamin Krajmalnik Cc: Tom Lane; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Howto: Using PITR recovery for standby replication Benjamin Krajmalnik wrote: > The particular table which was problematic (and for which I posted > another message due to the unique constraint violation which I am > seeing intermittently) is the one with the high insertion rate. The > sequence is currently being used to facilitate purginf of old records. How are you creating the dumps of the sequence and the table? If you do both separately (as in two pg_dump invocations with a -t switch each), that could explain your problem. This shouldn't really happen however, because the sequence dump should be emitted in a dump of the table, if the field is really of SERIAL or BIGSERIAL type. However I don't see any other way which would make the sequence go out of sync. -- Alvaro Herrera = http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ------_=_NextPart_001_01C664FA.A36A60C3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= Re: [ADMIN] Howto: Using PITR recovery for standby = replication=0A= =0A= =0A=
=0A=
Alvaro,
=0A=
 
=0A=
I am a newbie, so I = essentially invoked =0A= pg_dump from with pgAdmin3, with the defaults (including large =0A= objects).
=0A=
This is the command being =0A= issued:
=0A=
 
=0A=
.C:\Program =0A= Files\PostgreSQL\8.1\bin\pg_dump.exe -i -h 172.20.0.32 -p 5432 -U = postgres -F c =0A= -b -v -f "C:\Documents and Settings\administrator.MS\testbk.backup" =0A= events
=0A=
 
=0A=
What I assumed was happening = (and I may =0A= have very well been wrong) was that I was getting a consistent backup of = the =0A= object at the time that it was processed, but not the database as a =0A= whole.
=0A=
 
=0A=

=0A=
=0A= From: Alvaro Herrera =0A= [mailto:alvherre@commandprompt.com]
Sent: Thu 4/20/2006 10:02 =0A= PM
To: Benjamin Krajmalnik
Cc: Tom Lane; =0A= pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Howto: Using = PITR =0A= recovery for standby replication

=0A=
=0A=

Benjamin Krajmalnik wrote:

> The particular = table =0A= which was problematic (and for which I posted
> another message = due to the =0A= unique constraint violation which I am
> seeing intermittently) is = the one =0A= with the high insertion rate.  The
> sequence is currently = being used =0A= to facilitate purginf of old records.

How are you creating the = dumps of =0A= the sequence and the table?  If you do
both separately (as in = two =0A= pg_dump invocations with a -t switch each),
that could explain your =0A= problem.  This shouldn't really happen however,
because the = sequence =0A= dump should be emitted in a dump of the table, if
the field is really = of =0A= SERIAL or BIGSERIAL type.  However I don't see
any other way = which would =0A= make the sequence go out of sync.

--
Alvaro =0A= Herrera           =             &= nbsp;        =0A= http://www.CommandPrompt.com/<= BR>PostgreSQL =0A= Replication, Consulting, Custom Development, 24x7 =0A= support

=0A= =0A= =0A= ------_=_NextPart_001_01C664FA.A36A60C3--