Re: Can pg_dump make use of CURRENT/SESSION_USER

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: 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 16:24:03
Message-ID: CA+TgmoZzLOgGX9ryGC+LLOOO3XVkVACSk-Ywpo+_YzCgDf6bvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

--
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 Grzegorz Parka 2015-03-18 16:44:06 Re: GSoC idea - Simulated annealing to search for query plans
Previous Message Robert Haas 2015-03-18 16:23:13 Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0