Re: plpgsql.print_strict_params

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql.print_strict_params
Date: 2013-10-05 22:15:45
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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?

Marko Tiikkaja

Attachment Content-Type Size
print_strict_params_v4.patch text/plain 20.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2013-10-05 23:14:15 Re: pgbench - exclude pthread_create() from connection start timing
Previous Message Noah Misch 2013-10-05 22:10:02 Re: pgbench progress report improvements - split 3 v2 - A