From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: hubert depesz lubaczewski <depesz@depesz.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Pg 15 devel crashes when fetching data from table using cursor
Date: Thu, 10 Mar 2022 21:05:37 -0500
Message-ID: <762946.1646964337@sss.pgh.pa.us> (raw)
In-Reply-To: <20220311015030.irviiohj4e6rvdr5@alap3.anarazel.de>
References: <20220307094423.GA24798@depesz.com>
<20220311005045.vnwb3aa5htilh3rh@alap3.anarazel.de>
<CAH2-WzkHD5VDnswg_1qTQ45zqxQCAkkPwmmvL_8EX3Gut+mSbw@mail.gmail.com>
<20220311015030.irviiohj4e6rvdr5@alap3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> Another example of complete brokenness in the wider area is catalog accesses
> happening after PROC_IN_VACUUM is set. Afaict it's entirely incorrect to do
> any catalog accesses once set, because rows that are still needed for the
> catalog access can just be removed.
That seems like a fairly untenable design rule. Maybe we should rethink
what PROC_IN_VACUUM means/is used for.
regards, tom lane
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: tgl@sss.pgh.pa.us, andres@anarazel.de, pg@bowt.ie, depesz@depesz.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Pg 15 devel crashes when fetching data from table using cursor
In-Reply-To: <762946.1646964337@sss.pgh.pa.us>
* 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