Re: pgsql: Fix memory leak in PLySequence_ToJsonbValue()

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Fix memory leak in PLySequence_ToJsonbValue()
Date: 2018-06-16 12:44:30
Message-ID: 4aa93336-8c62-81fc-1977-2f3d8f6514b4@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 6/15/18 10:43, Alexander Korotkov wrote:
>> FWIW, I actually try to keep commit log lines to 75 characters, because
>> that's what displays nicely in "git log".
> Ok, thank you for the information. I'll also try to keep it to 75 characters.

This popular blog post recommends 72 characters and has some other
guidelines as well:

https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2018-06-16 13:08:36 pgsql: Remove AELs from subxids correctly on standby
Previous Message Tatsuo Ishii 2018-06-16 05:40:47 pgsql: Fix memory leak in BufFileCreateShared().