Re: Strange behavior with polygon and NaN - Mailing list pgsql-hackers

From gkokolatos@pm.me
Subject Re: Strange behavior with polygon and NaN
Date
Msg-id YP74y35GS9uaMLpKm0BiA_eK6etwydDvLfty44ykXV_cY74D9joc1H1xOI27Bq5L6YHwEV7huDY43hwbXu5i6RWK9vL53TgsbUtdVD26cP0=@pm.me
Whole thread Raw
In response to Re: Strange behavior with polygon and NaN  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Strange behavior with polygon and NaN  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, November 5, 2020 6:07 AM, Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:

> At Mon, 02 Nov 2020 14:43:32 +0000, Georgios Kokolatos gkokolatos@protonmail.com wrote in
>
> > Hi,
> > apologies for the very, very late reply to your fixes.
> > You have answered/addressed all my questions concerns. The added documentation
> > reads well, at least to a non native English speaker.
> > The patch still applies and as far as I can see the tests are passing.
> > It gets my :+1: and I am changing the status to "Ready for Committer".
> > For what little is worth, I learned a lot from this patch, thank you.
> > Cheers,
> > Georgios
> > The new status of this patch is: Ready for Committer
>
> Oh! Thanks. Since a part of this patch is committed (Thanks to Tom.)
> this is a rebased version on the commit.

I completely missed that a part got committed.

Thank you for your rebased version of the rest. I went through it
and my initial assessement of '+1' still stands.

The status remains to: Ready for Committer.

//Georgios

>
> regards.
>
>
--------------------------------------------------------------------------------------------------------------------------
>
> Kyotaro Horiguchi
> NTT Open Source Software Center


Attachment

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: WIP: BRIN multi-range indexes
Next
From: Magnus Hagander
Date:
Subject: Re: Prevent printing "next step instructions" in initdb and pg_upgrade