Robert Treat wrote:
> I think it is worth restating in stronger language, the potential overhead of
> raising notices or warning in such a large number of queries will be an
> upgrading show stopper for some people. (To the extent that for some, the
> release where this is a mandatory warning will be as much a show stopper as
> the release where the behavior is changed)
>
> IMHO we need at least 1 release with a GUC to control the warning (defaulting
> off initial, if people want the next release to default on, thats ok, but is
> probably a waste), so that people can turn it on/off in order to debug thier
> applications and make them compliant for upgrading to the next version. It
> doesnt much matter to me where you put this... 8.0.x, 8.1... it's just a
> question of where do you want to create a roadblock to upgrading, because the
> release where you force the warning always on your going to have raised the
> barrier to entry too high for some people.
The GUC will always be around to turn the warning on or off, until we go
with standard SQL strings, at which point there will be no warnings
generated.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073