Re: Triage on old commitfest entries - JSON_PATH

From: Erik Rijkers <er(at)xs4all(dot)nl>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Triage on old commitfest entries - JSON_PATH
Date: 2021-10-04 14:16:43
Message-ID: 33286615-96ae-2dd7-7dc1-5fc06a1cf350@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Op 04-10-2021 om 14:19 schreef Andrew Dunstan:
>
> On 10/3/21 3:56 PM, Erik Rijkers wrote:
>> Op 03-10-2021 om 21:14 schreef Tom Lane:
>>> As I threatened in another thread, I've looked through all of the
>>> oldest commitfest entries to see which ones should maybe be tossed,
>>>
>>> Patch        Age in CFs
>>
>> May I add one more?
>>
>> SQL/JSON: JSON_TABLE started 2018 (the commitfest page shows only 4 as
>> 'Age in CFs' but that obviously can't be right)
>>
>> Although I like the patch & new functionality and Andrew Dunstan has
>> worked to keep it up-to-date, there seems to be very little further
>> discussion. I makes me a little worried that the time I put in will
>> end up sunk in a dead project.
>>
>>
>
>
> I'm working on the first piece of it, i.e. the SQL/JSON functions.
>

Thank you. I am glad to hear that.

> cheers
>
>
> andrew
>
>
> --
> Andrew Dunstan
> EDB: https://www.enterprisedb.com
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-10-04 14:17:47 Re: [PATCH] Don't block HOT update by BRIN index
Previous Message Tom Lane 2021-10-04 13:56:53 Re: Duplicat-word typos in code comments