On Jun 17, 2005, at 4:34 PM, Greg Stark wrote:
And for an app issuing
hundreds or thousands of queries per minute (or even second) a
warning could
effectively be a showstopper. It could require disabling all
warnings in their
config to avoid filling their disk with Postgres logs in minutes.
Good point.
I would suggest this warning be disable-able with a GUC variable.
Otherwise
you're effectively giving no advance warning time to those users.
Perhaps NOTICE would be better, at least for the first step? People
might be more comfortable with that, as using backslash escaping
isn't really going to cause problems with this particular version,
but rather for future versions.
If postgres keeps advancing at the pace it's advancing now I might
suggest
waiting two release cycles instead of just one.
How's this for an idea?
Step 1 (8.1) NOTICE level (or some other level, lower than WARNING),
E'' and \' are available
Step 2 (8.2?) WARNING level, E'' and \' are available
Step 3 (8.3? 8.4?) E'' available, plain '' interpreted literally.
Michael Glaesemann
grzm myrealbox com
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
