| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql.print_strict_params |
| Date: | 2013-09-14 01:33:03 |
| Message-ID: | 20130914013303.GC5033@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marko Tiikkaja wrote:
> 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?
Seems like something that would be useful to change per function, rather
than globally, no?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-09-14 01:36:24 | Re: Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions) |
| Previous Message | Peter Eisentraut | 2013-09-14 01:30:39 | Re: [PATCH] Add transforms feature |