Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
Date: 2019-08-07 04:29:40
Message-ID: 65149e2b-1980-8f0d-668f-9d676f70e264@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

06.08.2019 9:24, Michael Paquier wrote:
> On Tue, Aug 06, 2019 at 03:21:11PM +0900, Michael Paquier wrote:
>> Note that the next set of minor versions is very close by (we are in a
>> cease-fire period for commits on back-branches), so this won't be
>> fixed in the upcoming releases.
> By the way, as long as I do not forget, could you add this patch to
> the next CF [1] as a bug fix? It is fine to add me as a reviewer.
>
> [1]: https://commitfest.postgresql.org/24/
Thank you Michael. It's done:
https://commitfest.postgresql.org/24/2231/

Best regards,
Alexander

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-08-07 09:54:44 Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
Previous Message Alexander Lakhin 2019-08-07 04:12:48 Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly