| From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Christoph Berg <cb(at)df7cb(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: postgresql.auto.conf and reload |
| Date: | 2014-06-25 13:16:52 |
| Message-ID: | 1403702212.24261.4.camel@asus-laptop-03.gunduz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, 2014-06-25 at 18:42 +0530, Amit Kapila wrote:
> This will happen without Alter System as well, if you change
> the value of port in postgresql.conf and try to load conf file with
> SIGHUP. You cannot reload PGC_POSTMASTER parameters without server
> restart.
Ok, but Christoph already started the server (successfully) with port
5494, so the pg_reload_conf() should ignore it in the next attempt.
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2014-06-25 13:17:25 | Re: postgresql.auto.conf and reload |
| Previous Message | Robert Haas | 2014-06-25 13:13:29 | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |