dbTalk Databases Forums  

[BUGS] BUG #2013: Assertion Failure

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] BUG #2013: Assertion Failure in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Joel Stevenson
 
Posts: n/a

Default [BUGS] BUG #2013: Assertion Failure - 11-02-2005 , 07:43 AM







The following bug has been logged online:

Bug reference: 2013
Logged by: Joel Stevenson
Email address: joelstevenson (AT) mac (DOT) com
PostgreSQL version: 8.1b3
Operating system: RHEL 3
Description: Assertion Failure
Details:

TRAP: FailedAssertion("!(!(tp.t_data->t_infomask & 0x0800))", File:
"heapam.c", Line: 1410)

This occured during a nightly mainentance run which sets the transaction
isolation level to SERIALIZABLE, moves records from 3 highly active tables
to 3 storage tables by creating a temp table and selecting candidate record
ids into it, then using that list via sub-select for the move ala "insert
into blah_storage (f1, f2, f3) select f1, f2, f3 from blah_active where f1
in (select f1 from move_records_tmp)"

After the move a VACUUM FULL ANALYZE is issued. It appears from the logs
written by the maintenace script that the assertion failure occured during
the vacuum.

I will install RC1 and see if it can be reproduced.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Reply With Quote
  #2  
Old   
Alvaro Herrera
 
Posts: n/a

Default Re: [BUGS] BUG #2013: Assertion Failure - 11-02-2005 , 08:20 AM






Joel Stevenson wrote:

Quote:
This occured during a nightly mainentance run which sets the transaction
isolation level to SERIALIZABLE, moves records from 3 highly active tables
to 3 storage tables by creating a temp table and selecting candidate record
ids into it, then using that list via sub-select for the move ala "insert
into blah_storage (f1, f2, f3) select f1, f2, f3 from blah_active where f1
in (select f1 from move_records_tmp)"

After the move a VACUUM FULL ANALYZE is issued. It appears from the logs
written by the maintenace script that the assertion failure occured during
the vacuum.

I will install RC1 and see if it can be reproduced.
Please be sure to also configure with --enable-debug (you obviously
already have --enable-cassert), and get a stack trace ("bt" command in
gdb) if at all possible. And keep the core dump somewhere safe -- we
will ask you questions about it.

If you already have a core dump, please provide a stack trace.

--
Alvaro Herrera http://www.advogato.org/person/alvherre
"La naturaleza, tan frágil, tan expuesta a la muerte... y tan viva"

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.