From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
Cc: | David Steele <david(at)pgmasters(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Teodor Sigaev <teodor(at)postgrespro(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: SQL/JSON in PostgreSQL |
Date: | 2017-03-07 19:38:57 |
Message-ID: | 20170307193857.cpdztwhaoloei4ba@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2017-03-07 12:21:59 +0300, Oleg Bartunov wrote:
> On 2017-03-03 15:49:38 -0500, David Steele wrote:
> > I propose we move this patch to the 2017-07 CF so further development
> > and review can be done without haste and as the standard becomes more
> > accessible.
+1
> I wanted to have one more good feature in 10 and let postgres be on par
> with other competitors. SQL/JSON adds many interesting features and users
> will be dissapointed if we postpone it for next two years. Let's wait for
> reviewers, probably they will find the patch is not very intrusive.
I think it's way too late to late for a patch of this size for 10. And I
don't think it's fair to a lot of other patches of significant size that
have been submitted way earlier, that also need reviewing resources, to
say that we can just see whether it'll get the required resources.
> We have a plenty of time and we dedicate one full-time developer for
> this project.
How about having that, and perhaps others, developer participate in
reviewing patches and getting to the bottom of the commitfest? Should
we end up being done early, we can look at this patch... There's not
been review activity corresponding to the amount of submissions from
pgpro...
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-03-07 20:24:55 | Re: Enabling parallelism for queries coming from SQL or other PL functions |
Previous Message | Pavel Stehule | 2017-03-07 19:26:39 | Re: New CORRESPONDING clause design |