Re: Refactor handling of database attributes between pg_dump and pg_dumpall

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Vaishnavi Prabakaran <vaishnaviprabakaran(at)gmail(dot)com>, 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-11-07 21:48:16
Message-ID: CA+Tgmobb1sWPDr73JzakZqY3PW9-797-dS8BD1eYhV482iTNPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 7, 2017 at 4:35 AM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> wrote:
> The newly added option is not recommended to be used in normal cases and
> it is used only for upgrade utilities.

I don't know why it couldn't be used in normal cases. That seems like
a totally legitimate thing for somebody to want. Maybe nobody does,
but I see no reason to worry if they do.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-11-07 21:48:33 Re: [PATCH] Overestimated filter cost and its mitigation
Previous Message Robert Haas 2017-11-07 21:46:48 Re: pg_stat_wal_write statistics view