From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup wish list |
Date: | 2016-09-14 00:24:39 |
Message-ID: | CAB7nPqRtE5vXZJBT0cZeQ8fPXuFVHhr2hPiTZoYqecxEYYyh0g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 14, 2016 at 6:52 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 9/12/16 3:31 PM, Tom Lane wrote:
>> Hm, there was just a kerfuffle about spelling things like this
>> "--no-clean" etc. I wasn't on board with removing existing spellings,
>> but surely all newly added switches should use the "no-" spelling?
>
> This is supposed to be parallel to initdb's option. So if we rename or
> migrate the one in initdb, then we can just hard-rename this one. But
> until that is decided, it seems better to keep it the same as initdb has
> right now.
PostgresNode.pm had better use the new --noclean option in its calls,
the new default is not useful for debugging. Please see attached.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
tap-noclean.patch | text/x-diff | 424 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2016-09-14 00:26:12 | Event trigger and CREATE/ALTER ROLE/USER |
Previous Message | Robert Haas | 2016-09-13 23:31:18 | Re: autonomous transactions |