From: José Luis Tallón <jltallon@adv-solutions.net>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Parser extensions (maybe for 10?)
Date: Wed, 13 Apr 2016 17:21:52 +0200
Message-ID: <570E6410.1060906@adv-solutions.net> (raw)
In-Reply-To: <CAMsr+YGSQJ=nG_QXxhtVQqWD=1awQ2+DqyD0CmKxk5qzE6X+Rg@mail.gmail.com>
References: <570C7B5A.9070309@gmail.com>
<CAMsr+YFHfJ7YKcRCUP_BdJZ+SHwoF9CdEvk8b-opVRDrHXf7uw@mail.gmail.com>
<570E53A1.2000405@adv-solutions.net>
<CAMsr+YGSQJ=nG_QXxhtVQqWD=1awQ2+DqyD0CmKxk5qzE6X+Rg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 04/13/2016 04:43 PM, Craig Ringer wrote:
> On 13 April 2016 at 22:11, José Luis Tallón
> <jltallon@adv-solutions.net <mailto:jltallon@adv-solutions.net>> wrote:
> [snip]
>
> I can certainly prepare a small patch for the first commitfest of
> 9.7 if this sounds viable.
>
>
> I'd be surprised if it was popular.
I am familiar with some cases where it would have been a lifesaver....
> It's hard to imagine a way to do it robustly when dealing with
> pre-lexer input, unless you're doing simple pattern matching to
> identify and replace whole statements.
INDEED. No intention whatsoever to do much more than that O:-)
/ J.L.
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: jltallon@adv-solutions.net, craig@2ndquadrant.com
Subject: Re: Parser extensions (maybe for 10?)
In-Reply-To: <570E6410.1060906@adv-solutions.net>
* 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