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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Дата
Msg-id 29313.1489759217@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 onnon-empty relations in  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Ответы Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 onnon-empty relations in  (Bruce Momjian <bruce@momjian.us>)
Список 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 по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: [COMMITTERS] pgsql: Rename "pg_clog" directory to "pg_xact".
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Rename "pg_clog" directory to "pg_xact".