From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Pg Bugs <pgsql-bugs@postgresql.org>
Cc: Andrew B <pgsql.20.drkshadow@spamgourmet.com>
Subject: Re: Snapshot leak warning with lo_export in subtransaction
Date: Mon, 27 Sep 2021 09:33:23 -0300
Message-ID: <202109271233.5zn5bqxn657w@alvherre.pgsql> (raw)
In-Reply-To: <32bf767a-2d65-71c4-f170-122f416bab7e@iki.fi>
On 2021-Sep-27, Heikki Linnakangas wrote:
> This should be backpatched to all supported versions. This adds an argument
> to 'inv_open' function, but I don't think there are extensions that use the
> inv_*() functions directly. inv_api.c relies on close_lo_relation() being
> called at the end of transaction, so I think an extension would find it hard
> to use those functions correctly, anyway.
Hmm, but you could also use a new value in its existing 'flags' argument
instead of changing ABI.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Voy a acabar con todos los humanos / con los humanos yo acabaré
voy a acabar con todos (bis) / con todos los humanos acabaré ¡acabaré! (Bender)
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: alvherre@alvh.no-ip.org, hlinnaka@iki.fi, pgsql.20.drkshadow@spamgourmet.com
Subject: Re: Snapshot leak warning with lo_export in subtransaction
In-Reply-To: <202109271233.5zn5bqxn657w@alvherre.pgsql>
* 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