Re: BUG #18483: Segmentation fault in tests modules - Mailing list pgsql-bugs

From Masahiko Sawada
Subject Re: BUG #18483: Segmentation fault in tests modules
Date
Msg-id CAD21AoBztjuNYD_Fhhn6J3+UBO74eTUHv3b4UN5p6f5gQB_waw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18483: Segmentation fault in tests modules  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: BUG #18483: Segmentation fault in tests modules
List pgsql-bugs
On Mon, Jun 10, 2024 at 9:33 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> Hi,
>
> Sorry for the late reply.
>
> On Wed, May 29, 2024 at 1:41 AM PG Bug reporting form
> <noreply@postgresql.org> wrote:
> >
> > The following bug has been logged on the website:
> >
> > Bug reference:      18483
> > Logged by:          Alexander Kozhemyakin
> > Email address:      a.kozhemyakin@postgrespro.ru
> > PostgreSQL version: 17beta1
> > Operating system:   ubuntu-22.04
> > Description:
> >
> > second case
> > echo "CREATE EXTENSION test_tidstore;
> > SELECT do_set_block_offsets(1, ARRAY[0]::int2[]);" >
> > src/test/modules/test_tidstore/sql/test_tidstore.sql
> > make check -C src/test/modules/test_tidstore
>
> Since the test script was modified so that it doesn't create tidstore
> before setting TIDs, the server crashed with SEGV. I remember that we
> used to check that the tidstore is already created before use, but we
> removed that check because it would not be very helpful; if a
> developer wiped out the create call then the test crashes pretty
> obviously[1]. Do we want to revive that check as raising an error is
> better than a SEGV?
>

I've attached the patch to fix the issue. I'm going to push it,
barring any objections.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #18483: Segmentation fault in tests modules
Next
From: Michael Paquier
Date:
Subject: Re: error "can only drop stats once" brings down database