It would be useful if you could toggle SQL statement logging without
restarting PostgreSQL and additionally if you could turn on selective SQL
logging. Additionally, it would be great if you could log SQL statements to
a separate file from the main log and in such a way that the statements are
seperated in an easily parsed form.
The runtime toggling of statement logging would also be most useful if you
could toggle it outside of a particular session. This is where the selective
SQL logging would be useful I think. Some selectable options that could be
useful:- by database- by user- by IP address
My current understanding, is that statements can be currently selectively
logged by:- whether they cause an error (log_min_error_statement)- whether they exceed a minimum amount of time
(log_min_duration_statement)-ddl and/or data modifications (log_statement)
I have no idea on how feasible this is. If it is feasible and nobody else is
interested in doing it but it would be accepted if somebody would write it,
I would be willing to start investigating how to do it.
-----Original Message-----
From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of karen hill
Sent: Friday, October 14, 2005 9:57 AM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] PostgreSQL roadmap for 8.2 and beyond.
Autovacuum is getting put into the 8.1 release which
is awesome. A lot of us are wondering now that
PostgreSQL has all the features that many of us need,
what are the features being planned for future
releases?
What do you see for 8.2 and beyond? What type of
features are you devs planning for 9.0? It would be
good if you could put up a place on your site so we
mortals can drool over up-coming postgresql features.
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster