| From: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Memory leak fix in psql |
| Date: | 2022-07-20 05:56:38 |
| Message-ID: | CAEG8a3++pap28Z5sdTpdifhKiAHVhOHJyNP0QW-xDtiz5W9aLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Got it, thanks!
On Wed, Jul 20, 2022 at 1:14 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Wed, Jul 20, 2022 at 12:51:24PM +0800, Junwang Zhao wrote:
> > Though the patch looks good, I myself think the patch should be edited
> > and submitted by Tang
> > It's easy to attach a fixed patch based on the comments of the thread,
> > but coins should be
> > given to Tang since he is the first one to find the mem leak.
>
> Please note that I sometimes edit slightly patches that I finish to
> merge into the tree, where the author listed in the commit log is the
> same as the original while I usually don't list mine. Credit goes
> where it should, and Tang is the one here who authored this patch.
> --
> Michael
--
Regards
Junwang Zhao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2022-07-20 06:12:13 | Re: Transparent column encryption |
| Previous Message | Thomas Munro | 2022-07-20 05:44:35 | Re: Remove fls(), use pg_bitutils.h facilities instead? |