From: | Jon Colverson <pgsql(at)vcxz(dot)co(dot)uk> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Attempt to re-archive existing WAL logs afterrestoringfrom backup |
Date: | 2007-06-02 00:07:44 |
Message-ID: | 4660B4D0.4090102@vcxz.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Simon Riggs wrote:
> I've spent some time re-examining the code and I can't see a route for
> the discussed problem to occur. All the main code paths do not exhibit
> this problem in 8.2, so I'm not sure where to go from here.
>
> If you can help further, please give me a shout.
Thanks a lot for looking into this.
I've attached a self-contained minimal shell script which sets up a
cluster and demonstrates the problem. I hope that will provide an
unambiguous description. I'm running it on Ubuntu 7.04 (i386) and the
script includes all the commands to build PostgreSQL from scratch, but
obviously you can snip that stuff out and change the paths to suit your
environment.
The script ends with the server log showing the archiver attempting to
re-archive the last log that was restored in the recovery procedure.
Thanks again.
--
Jon
Attachment | Content-Type | Size |
---|---|---|
pgsql-duplicate-xlog-demo.sh | text/plain | 2.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ezra Taylor | 2007-06-02 03:27:53 | Fwd: undefined reference to `SSL_CTX_set_client_cert_cb' |
Previous Message | Simon Riggs | 2007-06-01 20:07:46 | Re: Deletes hurt |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2007-06-02 00:08:26 | Re: Postmaster startup messages |
Previous Message | Tom Lane | 2007-06-01 23:46:48 | Re: BufFileWrite across MAX_PHYSICAL_FILESIZE boundary |