From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix snapshot reference leak if lo_export fails.
Date: Wed, 3 Nov 2021 19:47:23 +0200
Message-ID: <ff9c8400-382f-44c5-1729-8c759e7870ff@iki.fi> (raw)
In-Reply-To: <DBA08346-9962-4706-92D1-230EE5201C10@yesql.se>
References: <E1miCof-0006bt-DZ@gemulon.postgresql.org>
<DBA08346-9962-4706-92D1-230EE5201C10@yesql.se>
On 03/11/2021 13:06, Daniel Gustafsson wrote:
>> On 3 Nov 2021, at 10:44, Heikki Linnakangas <heikki.linnakangas@iki.fi> wrote:
>
>> Fix snapshot reference leak if lo_export fails.
>
> This commit seems to lack the update in largeobject_1 as per hamerkop in:
Fixed, thanks!
I'm a bit surprised none of the other Windows systems on the buildfarm
complained. The difference in largeobject_1 output is apparently that
the 'tenk.data' file uses Windows line endings. I guess that on all the
other Windows hosts, git has been configured to use Unix line endings.
- Heikki
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: hlinnaka@iki.fi, daniel@yesql.se
Subject: Re: pgsql: Fix snapshot reference leak if lo_export fails.
In-Reply-To: <ff9c8400-382f-44c5-1729-8c759e7870ff@iki.fi>
References: <E1miCof-0006bt-DZ@gemulon.postgresql.org> <DBA08346-9962-4706-92D1-230EE5201C10@yesql.se> <ff9c8400-382f-44c5-1729-8c759e7870ff@iki.fi>
* 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