From: Benjamin Krajmalnik <kraj@illumen.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Howto: Using PITR recovery for standby replication
Date: Thu, 20 Apr 2006 22:18:27 -0600
Message-ID: <8511B4970E0D124898E973DF496F9B4357E0F7@stash.stackdump.local> (raw)
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>
Alvaro,
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:
.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
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.
________________________________
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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kraj@illumen.com, alvherre@commandprompt.com, tgl@sss.pgh.pa.us
Subject: Re: Howto: Using PITR recovery for standby replication
In-Reply-To: <8511B4970E0D124898E973DF496F9B4357E0F7@stash.stackdump.local>
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> <8511B4970E0D124898E973DF496F9B4357E0F7@stash.stackdump.local>
* 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