Re: SPI/backend equivalent of extended-query Describe(statement)?

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Chapman Flack <chap(at)anastigmatix(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: SPI/backend equivalent of extended-query Describe(statement)?
Date: 2018-05-26 00:07:28
Message-ID: 878t871e2n.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Chapman Flack <chap(at)anastigmatix(dot)net> writes:
>> As for bringing it along to the modern API, am I on the right track
>> with writing a ParserSetupHook that's just a thin wrapper around
>> parse_variable_parameters ?

Tom> Seems reasonable from here.

That's what I did in pllua-ng. The tricky bit was in arranging to also
call check_variable_parameters; I considered skipping that part, but
that seemed like it could be potentially problematic.

https://github.com/pllua/pllua-ng/blob/master/src/spi.c#L266

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2018-05-26 00:34:42 Re: SPI/backend equivalent of extended-query Describe(statement)?
Previous Message Tom Lane 2018-05-26 00:02:24 Re: Timetz comparison