From: Tomas Vondra <tomas@vondra.me>
To: Ľuboslav Špilák <lspilak@microstep-hdo.sk>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Segmentation fault - PostgreSQL 17.0
Date: Sat, 9 Nov 2024 17:47:35 +0100
Message-ID: <c7e236d8-3eaa-440c-98fc-45c9cb8a0a08@vondra.me> (raw)
In-Reply-To: <VI1PR02MB633351521FD2DB430832394F8A5E2@VI1PR02MB6333.eurprd02.prod.outlook.com>
References: <VI1PR02MB63331C3D90E2104FD12399D38A5D2@VI1PR02MB6333.eurprd02.prod.outlook.com>
<ebd67ea5-5378-469d-b3cf-18af64ad2128@vondra.me>
<VI1PR02MB63335CB681D92A2EA70CA9678A5E2@VI1PR02MB6333.eurprd02.prod.outlook.com>
<b0440895-3f84-4d97-812e-a966a3c25396@vondra.me>
<VI1PR02MB633351521FD2DB430832394F8A5E2@VI1PR02MB6333.eurprd02.prod.outlook.com>
On 11/9/24 17:35, Ľuboslav Špilák wrote:
> Hello.
>
> After pg_upgrade there was 200 timeseries tables in xtimeseries database.
> Each about 2GB with two indexes. One Btree and second brin index. Brinis the case
> on two columns (timeseries_id, time).
>
> I created copy of one table and try change table to partitioned table,
> partigioned by time. One quartal to one partition.
>
> Analyse, vacuum table.
>
> Then i figured out it sigsegv on brin_page_items Function repeatedly.
>
> So THEN I try create new test table on pg17. I dont know now if I
> created table on different database or only on different schema, but on
> the same db cluster.
> Test table with one column with one brin index on that column. Insert
> only one row. I Vacuumed this test table. I try again sequence of three
> brin functions to check if brin index is computed. Third
> function brin_page_items caused sigsegv again.
>
I'm a bit confused about what exactly are the cases that fail. But if
you're observing crashes even on tables/indexes created on PG17 after
the upgrade, it's unlikely related to the upgrade.
Please, get the backtrace when you have access to the system.
Is there anything special about the system? Which repository are you
using for postgres packages?
regards
--
Tomas Vondra
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: tomas@vondra.me, lspilak@microstep-hdo.sk, pgsql-bugs@lists.postgresql.org
Subject: Re: Segmentation fault - PostgreSQL 17.0
In-Reply-To: <c7e236d8-3eaa-440c-98fc-45c9cb8a0a08@vondra.me>
* 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