Re: Parser extensions (maybe for 10?)

From: José Luis Tallón <jltallon(at)adv-solutions(dot)net>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parser extensions (maybe for 10?)
Date: 2016-04-13 15:21:52
Message-ID: 570E6410.1060906@adv-solutions.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/13/2016 04:43 PM, Craig Ringer wrote:
> On 13 April 2016 at 22:11, José Luis Tallón
> <jltallon(at)adv-solutions(dot)net <mailto:jltallon(at)adv-solutions(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-04-13 15:27:09 Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Previous Message Andres Freund 2016-04-13 15:18:01 Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <