Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M48420=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1dfAvF-000596-LJ
	for pgsql-bugs@arkaria.postgresql.org; Tue, 08 Aug 2017 20:16:13 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M48420=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1dfAvE-0006CU-P0
	for pgsql-bugs@arkaria.postgresql.org; Tue, 08 Aug 2017 20:16:12 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1dfAuX-0004wJ-Hh
	for pgsql-bugs@postgresql.org; Tue, 08 Aug 2017 20:15:29 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1dfAuQ-0003Ge-7M
	for pgsql-bugs@postgresql.org; Tue, 08 Aug 2017 20:15:29 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v78KFFEw015542;
	Tue, 8 Aug 2017 16:15:15 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Rick Otten <rottenwindfish@gmail.com>, ronan.dunklau@dalibo.com,
        PostgreSQL mailing lists <pgsql-bugs@postgresql.org>,
        Amit Kapila <amit.kapila16@gmail.com>,
        Robert Haas <robertmhaas@gmail.com>
Subject: 
In-reply-to: <20170808194943.smet3uuvtxats44v@alap3.anarazel.de>
References: <20170808194943.smet3uuvtxats44v@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Tue, 08 Aug 2017 12:49:43 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15540.1502223315.1@sss.pgh.pa.us>
Date: Tue, 08 Aug 2017 16:15:15 -0400
Message-ID: <15541.1502223315@sss.pgh.pa.us>
List-Archive: <http://archives.postgresql.org/pgsql-bugs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-bugs.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@postgresql.org>
List-Post: <mailto:pgsql-bugs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-bugs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
X-Mailing-List: pgsql-bugs
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

Andres Freund <andres@anarazel.de> writes:
> Perhaps, for v11, we should actually make sure there's no memory context
> etc set during _PG_init() to catch such problems earlier?

I don't see much of a way to do that in the "typical" case where
the library load happens as a result of a SQL command.  You can't
just say "oh, we're not in a transaction" and then later "wait,
yes we are".

Maybe we should recommend that extension authors test their libraries
in the preload scenario ...

			regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs