From: | Vaishnavi Prabakaran <vaishnaviprabakaran(at)gmail(dot)com> |
---|---|
To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Refactor handling of database attributes between pg_dump and pg_dumpall |
Date: | 2017-09-29 04:44:33 |
Message-ID: | CAOoUkxS+vS6ZZSTDoFmY-T1XCUJTM=FCj-B4nSYO0OxiGqbTYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Sat, Sep 9, 2017 at 1:29 PM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
wrote:
>
> Fixed patch is attached.
>
Patch applies and has lot of noise due to indent with spaces.
I did ran regression tests located in - src/test/regress,
src/test/modules/test_pg_dump, src/bin/pg_dump, src/bin/pg_upgrade folders
and no issues observed.
+ <term><option>--enable-pgdumpall-behaviour</option></term>
+ <listitem>
+ <para>
+ This option is for the use of <command>pg_dumpall</command> or
+ <command>pg_upgrade</command> utility to dump the database objects
+ by <application>pg_dump</application> for a complete dump.
+ This option can only be used with <option>-C/--create</option>.
+ Its use for other ourposes is not recommended or supported.
+ The behavior of the option may change in future releases without
notice.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
s/ourposes/purposes/
Option name "--enable-pgdumpall-behaviour" is very generic and it is
better to rename it to something that reflects its functionality like
--skip-default-db-create/--no-default-db-create
Thanks & Regards,
Vaishnavi,
Fujitsu Australia.
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2017-09-29 05:19:17 | Re: Bug with pg_basebackup and 'shared' tablespace |
Previous Message | Andres Freund | 2017-09-29 04:01:35 | Re: Minor codegen silliness in ExecInterpExpr() |