From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Rick Otten <rottenwindfish@gmail.com>
Cc: ronan.dunklau@dalibo.com, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Date: Tue, 08 Aug 2017 16:15:15 -0400
Message-ID: <15541.1502223315@sss.pgh.pa.us> (raw)
In-Reply-To: <20170808194943.smet3uuvtxats44v@alap3.anarazel.de>
References: <20170808194943.smet3uuvtxats44v@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
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
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, rottenwindfish@gmail.com, amit.kapila16@gmail.com, robertmhaas@gmail.com
Subject: Re:
In-Reply-To: <15541.1502223315@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