pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
Cc: Noah Misch <noah@leadboat.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: CM Team <cm@enterprisedb.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Semab Tariq <semab.tariq@enterprisedb.com>
Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Date: Sun, 31 Oct 2021 12:18:01 -0700
Message-ID: <20211031191801.q2anckkqsbd7oow2@alap3.anarazel.de> (raw)
In-Reply-To: <CANFyU95V9xW+0vrvF3A6v86u8E0zUkZVfWeFZe6KqWGgPeB=Jg@mail.gmail.com>
References: <20211019030212.GB3403374@rfd.leadboat.com>
	<20211024050028.GA3310519@rfd.leadboat.com>
	<20211024233502.GA3960658@rfd.leadboat.com>
	<20211028140459.GA284584@rfd.leadboat.com>
	<CANFyU942Dc=jVespMAJm=urAZb3mXc70MKkqFt8ZdKLgxyizqw@mail.gmail.com>
	<6EA60326-3CDF-4433-A190-F6D94A4B2ED5@yandex-team.ru>
	<CANFyU95S6C2q=eByr=8ocd4BJkgesYUTd7n4OsFzJ_t611NdWQ@mail.gmail.com>
	<CANFyU94A1kO4TKB4PODGYUqDRvPnBmc=P=EJR6_VxoFLiRjEMw@mail.gmail.com>
	<20211030191919.GA355663@rfd.leadboat.com>
	<CANFyU95V9xW+0vrvF3A6v86u8E0zUkZVfWeFZe6KqWGgPeB=Jg@mail.gmail.com>

Hi,

On 2021-10-31 13:01:00 +0530, Sandeep Thakkar wrote:
> > #1  0x40000000003fdc00:0 in equalTupleDescs (tupdesc1=0x60000000001f65e0,
> >
> >     tupdesc2=0x60000000001fba08)

Could you print out *tupdesc1, *tupdesc2? And best also
p tupdesc1->attrs[0]
p tupdesc1->attrs[1]
p tupdesc1->attrs[2]
p tupdesc2->attrs[0]
p tupdesc2->attrs[1]
p tupdesc2->attrs[2]


> > #2  0x40000000017f9660:0 in RelationClearRelation (
> >
> >     relation=0x60000000001f3730, rebuild=true)

Hm, too bad that we don't have working line numbers for some reason?


> > #3  0x40000000017fa730:0 in RelationFlushRelation
> > (relation=0x60000000001f3730)
> >
> > #4  0x40000000017fabb0:0 in RelationCacheInvalidateEntry
> > (relationId=27272)
> >
> > #5  0x40000000017c8f20:0 in LocalExecuteInvalidationMessage (
> >
> >     msg=0x60000000001a46b8)
> >
> > #6  0x40000000017c84e0:0 in ProcessInvalidationMessages (
> >
> >     group=0x60000000001a43e4, func=0x87ffffffef7b7250)
> >
> > #7  0x40000000017cb420:0 in CommandEndInvalidationMessages ()
> >
> > #8  0x40000000006b1c50:0 in AtCCI_LocalCache ()
> >
> > #9  0x40000000006b0910:0 in CommandCounterIncrement ()
> >
> > #10 0x4000000000807130:0 in create_toast_table (rel=0x60000000001f3730,
> >
> >     toastOid=0, toastIndexOid=0, reloptions=0, lockmode=8, check=true,
> >
> >     OIDOldToast=0)
> >
> > #11 0x4000000000805ac0:0 in CheckAndCreateToastTable (relOid=27272,
> >
> >     reloptions=0, lockmode=8, check=true, OIDOldToast=0) at toasting.c:88
> >
> > #12 0x4000000000805850:0 in AlterTableCreateToastTable (relOid=27272,
> >
> >     reloptions=0, lockmode=8) at toasting.c:62
> >
> > #13 0x4000000000aa9a30:0 in ATRewriteCatalogs (wqueue=0x87ffffffffffc3b0,
> >
> >     lockmode=8, context=0x87ffffffffffc590)


This crash could suggest that somehow the catalogs were corrupted and
that we're not reading back valid tupledescs from them. Hopefully we'll
know more after looking at the tupledescs.


Greetings,

Andres Freund





view thread (107+ messages)  latest in thread

Message-ID: <20211031191801.q2anckkqsbd7oow2@alap3.anarazel.de>
Permalink:  ../20211031191801.q2anckkqsbd7oow2@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20211031191801.q2anckkqsbd7oow2@alap3.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: andres@anarazel.de, sandeep.thakkar@enterprisedb.com, noah@leadboat.com, x4mmm@yandex-team.ru, cm@enterprisedb.com, pgsql-bugs@lists.postgresql.org, michael@paquier.xyz, tgl@sss.pgh.pa.us, pg@bowt.ie, semab.tariq@enterprisedb.com
  Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
  In-Reply-To: <20211031191801.q2anckkqsbd7oow2@alap3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox