| From: | Christoph Berg <cb(at)df7cb(dot)de> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: postgresql.auto.conf read from wrong directory |
| Date: | 2014-05-07 10:58:36 |
| Message-ID: | 20140507105835.GA20186@msgid.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Amit Kapila 2014-05-07 <CAA4eK1KTJkpVMnkOS2gFnnh2ZskO4ggDsPSWsHJbq1Cpu9EWRQ(at)mail(dot)gmail(dot)com>
> This problem occurs because we don't have the value of data_directory
> set in postgresql.conf by the time we want to parse .auto.conf file
> during server start. The value of data_directory is only available after
> processing of config files. To fix it, we need to store the value of
> data_directory during parse of postgresql.conf file so that we can use it
> till data_directory is actually set. Attached patch fixes the problem.
> Could you please once confirm if it fixes the problem in your
> env./scenario.
Hi Amit,
the patch fixes the problem. Thanks for looking into this.
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-05-07 11:00:43 | Re: Wanted: jsonb on-disk representation documentation |
| Previous Message | Simon Riggs | 2014-05-07 10:29:24 | Re: [v9.5] Custom Plan API |