Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in - Mailing list pgsql-committers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Date
Msg-id 29313.1489759217@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 onnon-empty relations in  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 onnon-empty relations in
List pgsql-committers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 03/17/2017 09:30 AM, Robert Haas wrote:
>> In the department of nitpicks, we usually try to write commit messages
>> so that the first line is a summary line which stands alone, and then
>> there's a blank line, and then more follows.  a la
>> https://chris.beams.io/posts/git-commit/#separate

> Yeah, In our case email subjects seem to be truncated at 64 chars, so
> it's best to stay under that limit if possible - 50 chars is sometimes
> pretty limiting.

FWIW, I usually try to keep line length in commit messages to <= 75
characters, as that is the wrap boundary in "git log" output.  It's
nice if the summary line can be made shorter, but it's often damn
hard to cram an adequate summary into 75 chars, let alone fewer.

(Links to mailing-list threads must ignore the length limit, sadly.)

            regards, tom lane


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: [COMMITTERS] pgsql: Rename "pg_clog" directory to "pg_xact".
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Rename "pg_clog" directory to "pg_xact".