Re: trap instead of error on 32 TiB table

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: trap instead of error on 32 TiB table
Date: 2021-09-09 13:30:57
Message-ID: CA+TgmoZD3xX5gBWrO6CEQ64ZNcMe3txTgb77-zNVrmptrcsndg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 9, 2021 at 7:52 AM Christoph Berg
<christoph(dot)berg(at)credativ(dot)de> wrote:
> Shouldn't the cassert build raise the ERROR instead as well?

We should definitely get an ERROR in both cases, not an assertion
failure. Exactly which ERROR we get seems negotiable.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-09-09 13:37:59 Re: Use generation context to speed up tuplesorts
Previous Message Drouvot, Bertrand 2021-09-09 13:16:00 Re: [BUG] Failed Assertion in ReorderBufferChangeMemoryUpdate()