Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nSUf7-0001Hi-60
	for pgsql-bugs@arkaria.postgresql.org; Fri, 11 Mar 2022 02:05:49 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nSUf6-0003dc-2A
	for pgsql-bugs@arkaria.postgresql.org; Fri, 11 Mar 2022 02:05:48 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nSUf5-0003aS-PY
	for pgsql-bugs@lists.postgresql.org; Fri, 11 Mar 2022 02:05:47 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nSUf3-0008RJ-Lw
	for pgsql-bugs@lists.postgresql.org; Fri, 11 Mar 2022 02:05:47 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22B25bMZ762947;
	Thu, 10 Mar 2022 21:05:37 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Peter Geoghegan <pg@bowt.ie>,
        hubert depesz lubaczewski <depesz@depesz.com>,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Pg 15 devel crashes when fetching data from table using cursor
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>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Thu, 10 Mar 2022 17:50:30 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <762945.1646964337.1@sss.pgh.pa.us>
Date: Thu, 10 Mar 2022 21:05:37 -0500
Message-ID: <762946.1646964337@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/762946.1646964337%40sss.pgh.pa.us>
Precedence: bulk

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