Re: pgsql: Fix snapshot reference leak if lo_export fails.

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix snapshot reference leak if lo_export fails.
Date: 2021-11-03 17:47:23
Message-ID: ff9c8400-382f-44c5-1729-8c759e7870ff@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 03/11/2021 13:06, Daniel Gustafsson wrote:
>> On 3 Nov 2021, at 10:44, Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Daniel Gustafsson 2021-11-03 19:27:33 Re: pgsql: Fix snapshot reference leak if lo_export fails.
Previous Message Heikki Linnakangas 2021-11-03 17:42:59 pgsql: Update alternative expected output file.