SQL-2016 in docs
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t76476psql -h localhost -U postgresBuilt from patchset v3 (message #3), July 28, 2026 at 04:12 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t76476_3 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t76476_3 && git checkout t76476_3Patchset v3 (message #3) is on t76476_3
I noticed that in our docs for PG12 there is no SQL-2016, but we actually
have JSON Path implementation committed, which is a part of SQL-2016
standard. One missing feature - is datetime support. Peter, will you
add this or I prepare the patch ?
Oleg
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 2019-05-12 10:14, Oleg Bartunov wrote:
I noticed that in our docs for PG12 there is no SQL-2016, but we actually
have JSON Path implementation committed, which is a part of SQL-2016
standard. One missing feature - is datetime support. Peter, will you
add this or I prepare the patch ?
I have now updated the feature list to SQL:2016. All the
SQL/JSON-related features are currently set to "NO". Please propose
patches to update that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On 2019-05-12 10:14, Oleg Bartunov wrote:
I noticed that in our docs for PG12 there is no SQL-2016, but we actually
have JSON Path implementation committed, which is a part of SQL-2016
standard. One missing feature - is datetime support. Peter, will you
add this or I prepare the patch ?
I did a rough check of the SQL:2016 JSON path specification versus our
regression tests, and came up with the attached supported feature list.
Would you like to confirm it?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
On 2019-05-12 10:14, Oleg Bartunov wrote:
I noticed that in our docs for PG12 there is no SQL-2016, but we actually
have JSON Path implementation committed, which is a part of SQL-2016
standard. One missing feature - is datetime support. Peter, will you
add this or I prepare the patch ?I did a rough check of the SQL:2016 JSON path specification versus our
regression tests, and came up with the attached supported feature list.
Would you like to confirm it?
I confirm it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 2019-05-30 16:34, Oleg Bartunov wrote:
On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:On 2019-05-12 10:14, Oleg Bartunov wrote:
I noticed that in our docs for PG12 there is no SQL-2016, but we actually
have JSON Path implementation committed, which is a part of SQL-2016
standard. One missing feature - is datetime support. Peter, will you
add this or I prepare the patch ?I did a rough check of the SQL:2016 JSON path specification versus our
regression tests, and came up with the attached supported feature list.
Would you like to confirm it?I confirm it.
pushed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services