Re: plpgsql.print_strict_params - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: plpgsql.print_strict_params
Date
Msg-id 52508F91.70008@joh.to
Whole thread Raw
In response to Re: plpgsql.print_strict_params  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: plpgsql.print_strict_params  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 04/10/2013 16:08, Robert Haas wrote:
> Yeah, that doesn't seem good.  How about writing the grammar production as
>
> '#' K_PRINT_STRICT_PARAMS option_value
>
> where option_value :=  T_WORD | unreserved_keyword;
>
> Then you don't need to make ON and OFF keywords; you can just use
> strcmp() against the option_value and either throw an error, or set
> the flag appropriately.

Something like the attached?


Regards,
Marko Tiikkaja

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: pgbench progress report improvements - split 3 v2 - A
Next
From: Noah Misch
Date:
Subject: Re: pgbench - exclude pthread_create() from connection start timing