Re: pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Gierth <rhodiumtoad(at)postgresql(dot)org>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Date: 2017-03-17 13:54:08
Message-ID: 4c5605f2-12d1-64ec-943c-bb484768f2f5@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-03-17 13:58:34 pgsql: Rename "pg_clog" directory to "pg_xact".
Previous Message Robert Haas 2017-03-17 13:36:50 pgsql: Remove dead link.