Re: Idea: closing the loop for "pg_ctl reload"

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Idea: closing the loop for "pg_ctl reload"
Date: 2015-03-03 17:09:29
Message-ID: 54F5EAC9.6030903@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/3/15 9:26 AM, Andres Freund wrote:
> On 2015-03-03 15:21:24 +0000, Greg Stark wrote:
>> Fwiw this concerns me slightly. I'm sure a lot of people are doing
>> things like "kill -HUP `cat .../postmaster.pid`" or the equivalent.
>
> postmaster.pid already contains considerably more than just the pid. e.g.
> 4071
> /srv/dev/pgdev-master
> 1425396089
> 5440
> /tmp
> localhost
> 5440001 82345992

If we already have all this extra stuff, why not include an actual error
message then, or at least the first line of an error (or maybe just swap
any newlines with spaces)?
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan de Visser 2015-03-03 17:11:35 Re: Idea: closing the loop for "pg_ctl reload"
Previous Message Andres Freund 2015-03-03 16:28:12 Re: autogenerated column names + views are a dump hazard