Re: Snapshot leak warning with lo_export in subtransaction

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>, Andrew B <pgsql(dot)20(dot)drkshadow(at)spamgourmet(dot)com>
Subject: Re: Snapshot leak warning with lo_export in subtransaction
Date: 2021-09-27 12:33:23
Message-ID: 202109271233.5zn5bqxn657w@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message hpc researcher_mspk 2021-09-28 06:15:34 Re: BUG #17200: PostgreSQL-Support Profile Guide Optimization(Clang/GCC)?
Previous Message Heikki Linnakangas 2021-09-27 10:55:00 Snapshot leak warning with lo_export in subtransaction