| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | jesper(dot)pedersen(at)redhat(dot)com, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: initdb w/ restart |
| Date: | 2017-11-02 17:30:03 |
| Message-ID: | a81d21d6-aaf4-dd69-4713-c0087a325c5c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/28/17 15:40, Jesper Pedersen wrote:
> In a case of
>
> initdb /tmp/pgsql
>
> followed by
>
> pg_ctl -D /tmp/pgsql/ -l /tmp/logfile restart
>
> you'll get
>
> pg_ctl: PID file "/tmp/pgsql/postmaster.pid" does not exist
> Is server running?
> starting server anyway
> pg_ctl: could not read file "/tmp/pgsql/postmaster.opts"
>
> The attached patch changes the message to "trying to start server
> anyway" to highlight it is an attempt, not something that will happen.
committed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-11-02 17:45:42 | Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM |
| Previous Message | Tom Lane | 2017-11-02 17:28:27 | Re: [HACKERS] pgsql: Fix freezing of a dead HOT-updated tuple |