On Wed, Mar 18, 2015 at 2:42 PM, Fabrízio de Royes Mello <
fabriziomello@gmail.com> wrote:
>
>
>
> On Wed, Mar 18, 2015 at 2:24 PM, Robert Haas <
robertmhaas@gmail.com> wrote:
> >
> > 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.
> >
>
> Ok.
>
>
> > >> > (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?
> >
>
> There's no need, sorry. I just misunderstood it first.
>
> I'll provide the patches.
>
Just one last doubt. Do we expose a new function called "current_database" like "current_catalog", "current_user", ... ?