Re: Can pg_dump make use of CURRENT/SESSION_USER - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Can pg_dump make use of CURRENT/SESSION_USER
Date
Msg-id CA+TgmoZHVj19GTXDCTaLCJhHe_T-cR_u-emZ2EoA=LaTPh3F9Q@mail.gmail.com
Whole thread Raw
In response to Re: Can pg_dump make use of CURRENT/SESSION_USER  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Responses Re: Can pg_dump make use of CURRENT/SESSION_USER
Re: Can pg_dump make use of CURRENT/SESSION_USER
List pgsql-hackers
On Wed, Mar 18, 2015 at 1:23 PM, Fabrízio de Royes Mello
<fabriziomello@gmail.com> wrote:
>> > If we ever implement something like
>> >
>> > COMMENT ON CURRENT_DATABASE IS ...
>> >
>> > it will be useful, because you will be able to restore a dump into
>> > another database and have the comment apply to the target database.
>
> I think it's simple to implement, but how about pg_dump... we need to add
> new option (like --use-current-database) or am I missing something ?

I think we'd just change it to use the new syntax, full stop.  I see
no need for an option.

>> > (Also, I wonder about
>> > ALTER USER foo IN DATABASE current_database ...
>> > because that will let us dump per-database user options too.)
>>
>> +1 for both of those ideas.
>
> Can you explain more about this idea?

Uh, what do you want explained?

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



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: Can pg_dump make use of CURRENT/SESSION_USER
Next
From: Andres Freund
Date:
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit