Re: trap instead of error on 32 TiB table - Mailing list pgsql-hackers

From Tom Lane
Subject Re: trap instead of error on 32 TiB table
Date
Msg-id 3568228.1631195095@sss.pgh.pa.us
Whole thread Raw
In response to trap instead of error on 32 TiB table  (Christoph Berg <christoph.berg@credativ.de>)
Responses Re: trap instead of error on 32 TiB table  (Christoph Berg <christoph.berg@credativ.de>)
List pgsql-hackers
Christoph Berg <christoph.berg@credativ.de> writes:
> I was wondering what happens when the 32 TiB per table limit is
> reached, so I faked 32767 1 GiB sparse files using dd and then tried
> inserting more rows.

> On a cassert-enabled build I got:

> TRAP: FailedAssertion("tagPtr->blockNum != P_NEW", File: "./build/../src/backend/storage/buffer/buf_table.c", Line:
125)

Can you provide a stack trace from that?

(or else a recipe for reproducing the bug ... I'm not excited
about reverse-engineering the details of the method)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Use generation context to speed up tuplesorts
Next
From: Christoph Berg
Date:
Subject: Re: trap instead of error on 32 TiB table