Hi Robert,
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 pro=
blem FIRST on VM. And by pausing/stopping/launching a VM it was easy to ge=
t these error back.
But since some weeks, I also had duplicates on real server. And same resul=
t if I try to launch a VACUUM: crash with the same assertion.Which "stack t=
race on the assertion failure" do you want to have ?
Regards,
Pascal BORSCHNECK
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 =
=3D=3D target)", File: "nbtpage.c", Line: 1166)
> From: robertmhaas@gmail.com
> To: borschneck@hotmail.com
> CC: pgsql-bugs@postgresql.org
>=20
> On Mon, Apr 18, 2011 at 5:16 AM, BORSCHNECK Pascal
> <borschneck@hotmail.com> wrote:
> > Because I noticed that doing a pause to a VM (to make a VM copy for exa=
mple)
> > often creates duplicates key problems error in the logs.
>=20
> That's kind of surprising, but I can't help wondering if it's a bug in
> what virtualization tool you are using.
>=20
> Any way to get a stack trace on the assertion failure?
>=20
> --=20
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
=20=09=09=20=09=20=20=20=09=09=20=20=