Re: pg_dump does not include database-level user-defined GUC variables? - Mailing list pgsql-general

From Pavel Stehule
Subject Re: pg_dump does not include database-level user-defined GUC variables?
Date
Msg-id CAFj8pRCk7rZ99jcwVCar7Srw4G=Ykyc6VTo6og2+AGY1Ykfjpw@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump does not include database-level user-defined GUC variables?  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: pg_dump does not include database-level user-defined GUC variables?  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-general


2014-09-16 17:39 GMT+02:00 Kevin Grittner <kgrittn@ymail.com>:
Abelard Hoffman <abelardhoffman@gmail.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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: pg_dump does not include database-level user-defined GUC variables?
Next
From: Willy-Bas Loos
Date:
Subject: Re: 2 left joins causes seqscan