pg.ddx.io pgsql-hackers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Stas Kelvich <s.kelvich@postgrespro.ru>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: David Steele <david@pgmasters.net>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Oleg Bartunov <obartunov@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Subject: Re: jsonpath
Date: Thu, 08 Nov 2018 00:12:55 -0500
Message-ID: <30161.1541653975@sss.pgh.pa.us> (raw)
In-Reply-To: <3d3d4876-3084-c339-ce0a-d8b7e96a38d3@2ndquadrant.com>
References: <CAA8=A796mY7kJdKARt7B+faW70-c8mRh+Ff_joBJ+NyCFLv3Gg@mail.gmail.com>
<19506.1521524178@sss.pgh.pa.us>
<880bcbc6-1dba-cf82-7945-c10528f602c4@postgrespro.ru>
<892ae4c4-e549-ab21-c57c-37c5fd47fda0@pgmasters.net>
<8dd1cd76-cd4e-9be7-9515-ef0b8b21cb67@postgrespro.ru>
<CAEepm=0jJ4fkEWLHc2Rqt5F4Und6qd+60pxFQmCnbf0nYYjrcg@mail.gmail.com>
<3bc15ece-5219-e4ca-0b5c-fcd2b276aa26@postgrespro.ru>
<4e2aaa88-3bbf-6af3-8dad-d5687fbec89f@postgrespro.ru>
<42272F2B-16D1-43D6-B22F-273AE1DA6D6B@postgrespro.ru>
<715c1c44-9bb9-6b9f-7c59-61b66578f107@postgrespro.ru>
<20181002023317.GI11712@paquier.xyz>
<063560d8-bc0b-945b-8796-5ba998d79dc6@2ndquadrant.com>
<9a175c2d-b0a9-475f-078b-febc185282ff@postgrespro.ru>
<3d3d4876-3084-c339-ce0a-d8b7e96a38d3@2ndquadrant.com>
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> BTW is the v19 really just a rebase of the preceding version?
> I'm asking because v18 was adding two types into pg_type.dat, namely
> jsonpath (6050) and _jsonpath (6051), while v19 only adds jsonpath
> (6050).
I haven't looked at this patch, but manual generation of array type entries
is obsolete since 3dc820c43e427371b66d217f2bd5481fc9ef2e2d. There should
still be a mention of the OID to use for the array type though ...
regards, tom lane
view thread (198+ messages) latest in thread
Message-ID: <30161.1541653975@sss.pgh.pa.us> Permalink: ../30161.1541653975@sss.pgh.pa.us/ Also on: postgresql.org/message-id/30161.1541653975@sss.pgh.pa.us ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-hackers@postgresql.org Cc: tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com, n.gluhov@postgrespro.ru, michael@paquier.xyz, s.kelvich@postgrespro.ru, thomas.munro@enterprisedb.com, david@pgmasters.net, andrew.dunstan@2ndquadrant.com, a.korotkov@postgrespro.ru, robertmhaas@gmail.com, obartunov@gmail.com, pavel.stehule@gmail.com Subject: Re: jsonpath In-Reply-To: <30161.1541653975@sss.pgh.pa.us> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox