From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Abelard Hoffman <abelardhoffman(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump does not include database-level user-defined GUC variables? |
Date: | 2014-09-16 15:43:08 |
Message-ID: | CAFj8pRCk7rZ99jcwVCar7Srw4G=Ykyc6VTo6og2+AGY1Ykfjpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2014-09-16 17:39 GMT+02:00 Kevin Grittner <kgrittn(at)ymail(dot)com>:
> Abelard Hoffman <abelardhoffman(at)gmail(dot)com> wrote:
>
> > I have a user-defined GUC variable that was set at the db level. e.g.,
> >
> > ALTER DATABASE mydb SET myapp.user_id TO '1'
> >
> > Works fine. When I do a pg_dump, however, that variable isn't included.
> > Is that expected? It's not really an attribute of the database?
>
> That sort of information *about the database* is stored at the
> cluster level, not in the database itself. Take a look at
> pg_dumpall.
>
aha, I though it is bug
I don't think so this design is well - this settings is strictly related to
database. So there should be some option for dumping these options too.
Regards
Pavel
>
> --
> Kevin Grittner
> EDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Willy-Bas Loos | 2014-09-16 16:38:51 | Re: 2 left joins causes seqscan |
Previous Message | Kevin Grittner | 2014-09-16 15:39:02 | Re: pg_dump does not include database-level user-defined GUC variables? |