Re: pg_dumpall --exclude-database option

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: pg_dumpall --exclude-database option
Date: 2018-10-31 17:04:02
Message-ID: c9d2c989-3ee7-f371-c72f-e1b389738a00@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/31/2018 12:44 PM, Fabien COELHO wrote:
>
> Hello Andrew,
>
>> This patch addresses all these concerns.
>
> Patch v4 applies cleanly, compiles, doc generation ok, global & local
> tests ok.
>
> Tiny comments: there is a useless added blank line at the beginning of
> the added varlistenry.
>
> I have recreated the CF entry and put the patch to ready... but I've
> must have mixed up something because now there are two entries:-(
>
> Could anywone remove the duplicate entry (1859 & 1860 are the same)?
> Peter??
>

:-( My fault, I just created a new one.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-10-31 17:09:53 Re: pg_promote not marked as parallel-restricted in pg_proc.dat
Previous Message Robert Haas 2018-10-31 16:59:21 Re: WIP: Avoid creation of the free space map for small tables