From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | logging statement levels |
Date: | 2004-01-05 21:45:09 |
Message-ID: | 3FF9DAE5.9010405@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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.
Also, I assume "modification statements" means insert/update/delete, or
are we talking about DDL mods (like "alter table")?
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.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Steven Vajdic | 2004-01-05 22:46:22 | UNSUBSCRIBE |
Previous Message | Andrew Dunstan | 2004-01-05 21:20:38 | Re: PL/Java issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Kurt Roeckx | 2004-01-05 22:18:50 | Re: remove obsolete NULL casts |
Previous Message | Neil Conway | 2004-01-05 21:44:23 | minor smgr code cleanup |