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-14 01:55:40
Message-ID: 5233C21C.3030203@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-09-14 03:33, Alvaro Herrera wrote:
> Marko Tiikkaja wrote:
>> 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?

The way I see it, STRICT is like an assertion, and you *would* pretty
much always change it globally.

However, it would be useful to also have the option to set it for a
single function only. Will look into that. Thanks for the suggestion!

Regards,
Marko Tiikkaja

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-09-14 02:20:11 Re: record identical operator
Previous Message Peter Eisentraut 2013-09-14 01:36:24 Re: Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)