From: Nico Williams <nico@cryptonector.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Christian Convey <christian.convey@gmail.com>
Cc: Petr Jelinek <petr@2ndquadrant.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: David Fetter <david@fetter.org>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Tackling JsonPath support
Date: Mon, 5 Dec 2016 10:42:14 -0600
Message-ID: <20161205164213.GA32541@localhost> (raw)
In-Reply-To: <CA+TgmoZBcdKO=v9rHmf=KhNjgPvCL_PUmKwZOHJTUgcuP1hBrg@mail.gmail.com>
References: <20161128192343.GD11117@localhost>
<CAPfS4ZwgHT5FkRm8LE0ucG97e36ziBm0Pc-GkyGC15ksTwVFpw@mail.gmail.com>
<CAFj8pRAtvZAtA2OBiyZyjf+AC24g6oSuKsbA8uWGZFZOoq=hDw@mail.gmail.com>
<CAPfS4ZzcAdX6S3389rO-xfULvYuvD6VCACoxNJK=sUmhsnj0ow@mail.gmail.com>
<CAFj8pRC8FFX9=+yi_im8bBJP0GJrv92hSuoFUH0nft62QLk0oQ@mail.gmail.com>
<80228378-f5ba-1291-872b-9812e103e37c@2ndquadrant.com>
<CAPfS4Zyjh4F9OWTsc4EJKh=1NR_qU+7GLZr0BC4bq9KULEf75Q@mail.gmail.com>
<CA+TgmoZ28byiVjXTHO=B3jbOWcVk7dVySvJGc7wBF0ecPjOBhg@mail.gmail.com>
<20161202213223.GJ24797@localhost>
<CA+TgmoZBcdKO=v9rHmf=KhNjgPvCL_PUmKwZOHJTUgcuP1hBrg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Mon, Dec 05, 2016 at 11:28:31AM -0500, Robert Haas wrote:
> The overall need is that it needs to be possible for PostgreSQL to
> throw an ERROR, and thus longjmp, without leaking resources.
As long as one can interpose jump buffers, that should be possible.
> Sometimes those errors happen asynchronously due to query cancel or
> replication conflicts or similar, and those don't have to be processed
> at once but the delay can't be unbounded or more than some modest
> fraction of a second. Integrating with PostgreSQL's memory-context
> stuff might make that or other resource leak problems easier, or it
> might not. To really get a clear notion of what would be involved, I
> think you'd probably need to produce a prototype patch and submit it
> here for review to really find out what issues people see with it.
Understood. Thanks.
> Library integrations are tricky but, since you wrote JQ and seem
Just to be clear, Stephen Dolan wrote jq. I've added to, and maintained
jq, to be sure, but I would not want to take credit from Stephen.
> potentially willing to modify it to work with PostgreSQL better, this
> one might be a lot less painful than some. I can't promise we'd
> accept an integration even if you came up with a patch, but I see
> looking back over this thread that there are several people cautiously
> supporting the idea of using JQ in some form, which is promising.
Fair enough. I won't be able to work on an integration for a few more
months, so we'll see (and Stephen might well veto some such changes to
jq), and it is time for me to shut up about this for now. Thanks for
the very useful comments, and sorry for the noise.
Nico
--
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: nico@cryptonector.com, robertmhaas@gmail.com, christian.convey@gmail.com, petr@2ndquadrant.com, pavel.stehule@gmail.com, david@fetter.org, tgl@sss.pgh.pa.us
Subject: Re: Tackling JsonPath support
In-Reply-To: <20161205164213.GA32541@localhost>
* 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