Re: Bug with pg_basebackup and 'shared' tablespace

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: Bug with pg_basebackup and 'shared' tablespace
Date: 2017-09-13 16:01:43
Message-ID: 295611B3-2828-4562-B97A-9853E8E24D93@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 15 May 2017, at 07:26, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
> On Tue, May 2, 2017 at 2:28 AM, Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info> wrote:
>
>> I will submit this patch in the current commit fest.
>
> I have not spotted any flaws in the refactored logic.

This patch no longer applies, could you take a look at it and submit a new
version rebased on top of HEAD?

cheers ./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-09-13 16:06:40 Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b
Previous Message Konstantin Knizhnik 2017-09-13 16:00:01 Re: Surjective functional indexes