Re: logging statement levels
От | Bruce Momjian |
---|---|
Тема | Re: logging statement levels |
Дата | |
Msg-id | 200403310242.i2V2gB000840@candle.pha.pa.us обсуждение исходный текст |
Ответ на | logging statement levels (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: logging statement levels
|
Список | pgsql-hackers |
Andrew Dunstan wrote: > I wrote: > > > > > > > If nobody is working on this I am prepared to look at it: > > > > . Allow logging of only data definition(DDL), or DDL and modification > > statements > > > > > > Here are some options: > > 1. change the type of "log_statement" option from boolean to string, > with allowed values of "all, mod, ddl, none" with default "none". > 2. same as 1. but make boolean true values synonyms for "all" and > boolean false values synonyms for "none". > 3. keep "log_statement" option as now and add a new option > "log_statement_level" with the same options as 1. but default to "all", > which will have no effect unless "log_statement" is true. I like 1. > Also, I assume "modification statements" means insert/update/delete, or Yes. > are we talking about DDL mods (like "alter table")? Alter is DDL. > Finally, what about functions that have side effects? It would be nice > to be able to detect the statements to be logged at the syntactic level, > but it strikes me that that might not be possible. Not possible. -- 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
В списке pgsql-hackers по дате отправления: