Re: plpgsql.print_strict_params

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql.print_strict_params
Date: 2013-09-13 22:42:33
Message-ID: 523394D9.5080909@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-09-14 00:39, Alvaro Herrera wrote:
>> set plpgsql.print_strict_params to true;
>
> Hmm, shouldn't this be a compile option? See the "comp_option"
> production in pl_gram.y for existing examples.

I thought about that, but it seemed more like a runtime option to me.
Any particular reason you think it would be better as a compile time option?

Regards,
Marko Tiikkaja

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Poole 2013-09-13 23:41:25 patch: add MAP_HUGETLB to mmap() where supported (WIP)
Previous Message Alvaro Herrera 2013-09-13 22:39:27 Re: plpgsql.print_strict_params