Re: BUG #5984: Got FailedAssertion("!(opaque->btpo_prev == target)", File: "nbtpage.c", Line: 1166)

Hi Robert,

I'll try this, if possible, with one of the server with "duplicates".

I found another problem to generate duplicates: play with DB with no disk space left.

After that, if I launch a VACCUM FULL, same crash.

Global question as I didn't find it: are "ERROR: duplicate key value violates unique constraint" fatal errors ? As they may (most of the time) be corrected with reindexdb --all

Someone told me some weeks ago "it's only a notice, the database is not corrupted" ...

Regards,

Pascal BORSCHNECK

Port: +33 (0)630495775

borschneck(at)hotmail(dot)com

http://www.arfy.fr
My profiles:

Chat borschneck(at)hotmail(dot)com arfyfr pascal(dot)borschneck(at)gmail(dot)com

Arfy's blog Geeky-gadgets.com - Eton Raptor Solar Survival Tool

Le 23/05/2011 19:12, Robert Haas a écrit:

On Mon, May 16, 2011 at 8:04 AM, Pascal Borschneck borschneck(at)hotmail(dot)com wrote:

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 inwhat 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 ?

Well, when a backend crashes, it would be helpful to know what was going on when it crashed. See this wiki page:

http://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

--

Robert Haas

EnterpriseDB: http://www.enterprisedb.com

The Enterprise PostgreSQL Company