Re: [PATCHES] Escape handling in strings
От | Michael Glaesemann |
---|---|
Тема | Re: [PATCHES] Escape handling in strings |
Дата | |
Msg-id | 90F1CF7B-6B90-4E5E-AAD3-58EE622ED81C@myrealbox.com обсуждение исходный текст |
Ответ на | Re: [PATCHES] Escape handling in strings (Greg Stark <gsstark@mit.edu>) |
Ответы |
Re: [PATCHES] Escape handling in strings
|
Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: