Re: Patch to implement pg_current_logfile() function

From: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to implement pg_current_logfile() function
Date: 2017-02-15 20:53:34
Message-ID: 20170215145334.2c5c6b04@slate.meme.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 15 Feb 2017 15:23:00 -0500
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> + errhint("The supported log formats are
> \"stderr\""
> + " and \"csvlog\".")));
>
> I think our preferred style is not to break strings across lines like
> this.

How do you do that and not exceed the 80 character line limit?
Just ignore the line length limit?

Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-02-15 21:03:06 Re: Missing CHECK_FOR_INTERRUPTS in hash joins
Previous Message David G. Johnston 2017-02-15 20:33:52 Re: [PROPOSAL] Temporal query processing with range types