Sorry for the late reply, I was not here last week.
About your question: "That's kind of surprising, but I can't help wondering if it's a bug in what virtualization tool you are using."I noticed the problem FIRST on VM. And by pausing/stopping/launching a VM it was easy to get these error back.
But since some weeks, I also had duplicates on real server. And same result if I try to launch a VACUUM: crash with the same assertion.Which "stack trace on the assertion failure" do you want to have ?
Arfy's blog http://www.arfy.fr
> Date: Wed, 11 May 2011 15:48:29 -0400
> Subject: Re: [BUGS] BUG #5984: Got FailedAssertion("!(opaque->btpo_prev == target)", File: "nbtpage.c", Line: 1166)
> From: robertmhaas(at)gmail(dot)com
> To: borschneck(at)hotmail(dot)com
> CC: pgsql-bugs(at)postgresql(dot)org
> On Mon, Apr 18, 2011 at 5:16 AM, BORSCHNECK Pascal
> <borschneck(at)hotmail(dot)com> wrote:
> > Because I noticed that doing a pause to a VM (to make a VM copy for example)
> > often creates duplicates key problems error in the logs.
> That's kind of surprising, but I can't help wondering if it's a bug in
> what virtualization tool you are using.
> Any way to get a stack trace on the assertion failure?
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Bruce Momjian||Date: 2011-05-16 15:22:18|
|Subject: Re: BUG #6026: redundant sentences?|
|Previous:||From: Matthijs Bomhoff||Date: 2011-05-16 09:10:23|
|Subject: Re: Re: Bug with STABLE function using the wrong snapshot (probably during planning) |