| From: | Vasiliy G Tolstov <v(dot)tolstov(at)selfip(dot)ru> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Shoaib Mir <shoaibmir(at)gmail(dot)com>, Anh Ky Huynh <xkyanh(at)gmail(dot)com>, PostgreSQL Admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: graceful reload |
| Date: | 2010-06-04 06:07:12 |
| Message-ID: | 1275631632.28777.0.camel@work.selfip.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
В Чтв, 03/06/2010 в 13:07 -0400, Greg Smith пишет:
> Vasiliy G Tolstov wrote:
> > In config file some in of this settings exists comment line like
> > "changes require restart". This is mean exactly restart or reload can do
> > this?
> >
>
> Run this:
>
> $ psql -c "select name,context from pg_settings"
>
> This will sort out which settings are in which category definitively,
> rather than relying on the sometimes ambiguous comments in the file.
> Settings that say "postmaster" require a full database restart. Ones
> labeled "sighup" can be changed in the postgresql.conf and then the
> server signaled to use them, most easily with:
>
> pg_ctl reload
> -OR-
> psql -c "select pg_reload_conf()"
>
> Ones labeled "user" you can actually change for any user at any time
> during their session. Modifying the defaults and then executing the
> sighup procedure will make those new defaults active, but not for any
> clients that already have open connections.
>
> I recommend using SHOW or looking at pg_settings after making a change
> and reloading the server config to confirm it took.
>
Ok, Thank You very much! This is really helpful.
--
Vasiliy G Tolstov <v(dot)tolstov(at)selfip(dot)ru>
Selfip.Ru
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2010-06-04 10:59:39 | Re: PITR Recovery Question |
| Previous Message | Gnanakumar | 2010-06-04 05:05:45 | Re: PITR Recovery Question |