| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Fabrízio Mello <fabriziomello(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Can pg_dump make use of CURRENT/SESSION_USER |
| Date: | 2015-03-18 17:24:31 |
| Message-ID: | CA+TgmoZHVj19GTXDCTaLCJhHe_T-cR_u-emZ2EoA=LaTPh3F9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 18, 2015 at 1:23 PM, Fabrízio de Royes Mello
<fabriziomello(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-03-18 17:26:53 | Re: Rethinking the parameter access hooks for plpgsql's benefit |
| Previous Message | Fabrízio de Royes Mello | 2015-03-18 17:23:21 | Re: Can pg_dump make use of CURRENT/SESSION_USER |