From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Postgresql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
Date: Mon, 08 Sep 2003 16:28:38 -0400
Message-ID: <453.1063052918@sss.pgh.pa.us> (raw)
In-Reply-To: <3F5CC9FE.5030103@dunslane.net>
References: <15403.1063035632@sss.pgh.pa.us>
<3F5CAC68.30502@pse-consulting.de>
<m3d6eb1bmu.fsf@varsoon.wireboard.com>
<19042.1063039625@sss.pgh.pa.us>
<3F5CC9FE.5030103@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> How would we "deprecate" it exactly? Throw a NOTICE?
>>
> Release notes, I guess. A NOTICE would be fine as long as it didn't
> result in a flood of them. If that happened once at parse time that
> should be fine, I think.
It would be relatively difficult to do that; given the way plpgsql is
structured, a runtime message would be a lot easier.
> What's the practice in deprecating other "features"?
We generally don't ;-). Certainly 7.4 contains bigger incompatible
changes than this one, and so have most of our prior releases.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
In-Reply-To: <453.1063052918@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox