Re: Can pg_dump make use of CURRENT/SESSION_USER

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Robert Haas <robertmhaas(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:23:21
Message-ID: CAFcNs+p6iq0US8pyx2nTv_+ooFzssRT700N6icqk966O+sSmaQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 18, 2015 at 1:24 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Tue, Mar 17, 2015 at 1:24 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(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 ?

> > (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?

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-03-18 17:24:31 Re: Can pg_dump make use of CURRENT/SESSION_USER
Previous Message Robert Haas 2015-03-18 17:17:36 Re: Rethinking the parameter access hooks for plpgsql's benefit