Re: Attempt to re-archive existing WAL logs afterrestoringfrom backup

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Jon Colverson" <pgsql(at)vcxz(dot)co(dot)uk>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Attempt to re-archive existing WAL logs afterrestoringfrom backup
Date: 2007-06-01 20:02:19
Message-ID: 1180728140.26297.261.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Fri, 2007-06-01 at 12:02 +0100, Simon Riggs wrote:
> On Thu, 2007-05-31 at 16:09 +0100, Jon Colverson wrote:
> > >
> > >> This looks like a bug to me. Any thoughts?
> > >
>
> > No; nothing is touching the archive except for the archive_command being
> > run by PostgreSQL.
>
> Jon,
>
> You're still troubled by what you've seen?
>
> Can you start from the beginning again and describe exactly what set of
> circumstances you're in. I want to remove any bug or doubt that there is
> one lurking.

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.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Simon Riggs 2007-06-01 20:07:46 Re: Deletes hurt
Previous Message Dan Harris 2007-06-01 18:51:54 Re: Function to offset current timestamp

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-06-01 20:05:47 Re: Command tags in create/drop scripts
Previous Message Simon Riggs 2007-06-01 19:54:54 Re: Do we need a TODO? (was Re: Concurrently updatinganupdatable view)