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

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

On 3/3/15 7:34 PM, Jim Nasby wrote:
> Definitely no multi-line. If we keep that restriction, couldn't we just
> dedicate one entire line to the error message? ISTM that would be safe.

But we have multiline error messages. If we put only the first line in
the pid file, then all the tools that build on this will effectively
show users truncated information, which won't be a good experience. If
we don't put any error message in there, then users or tools will be
more likely to look up the full message somewhere else.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-03-04 21:56:53 Re: MD5 authentication needs help
Previous Message Peter Eisentraut 2015-03-04 21:45:12 Re: New CF app deployment