From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | 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-15 14:16:04 |
Message-ID: | CAPpHfdsWBQAK2W=VO6U=iV4Xj40GxNbH8rqt7TQowGgAMD0H0g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Fri, Jun 15, 2018 at 4:46 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> > I'm sorry for misformatting commit message. I'll be more careful
> > about that in future.
>
> Maybe I just lack caffeine, but I don't see anything especially
> wrong with what you wrote?
It doesn't contain something particular wrong, but it's just badly
formatted. As I can see, we're keeping lines in commit messages no
longer than 80 characters when possible. I've commit message with 158
characters line for no reason. It was just because I wrote this
commit message with word wrapping enabled.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-06-15 14:25:27 | Re: pgsql: Fix memory leak in PLySequence_ToJsonbValue() |
Previous Message | Tom Lane | 2018-06-15 13:46:45 | Re: pgsql: Fix memory leak in PLySequence_ToJsonbValue() |