logging queries and time used

[stig erikson]

Hi.
i would like to log every single query coming in to the database into a
table. i would like the log to include the entire query and execution
time and execution cost, and if possible the user that executed the query.

A trigger is what i was thinking of, but how can i find out the actual
query, the time it took to execute it, etc.?

stig

[Michael Fuhr]

On Fri, Oct 29, 2004 at 11:18:48PM +0200, stig erikson wrote:

i would like to log every single query coming in to the database into a
table. i would like the log to include the entire query and execution
time and execution cost, and if possible the user that executed the query.

A trigger is what i was thinking of, but how can i find out the actual
query, the time it took to execute it, etc.?

See the "Error Reporting and Logging" section of the documentation:

http://www.postgresql.org/docs/7.4/s...CONFIG-LOGGING

You might be able to feed the logging output to a script that inserts
into a table, but make sure that important log messages are also
stored outside the database to avoid losing them if trouble arises.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

[Michael Fuhr]

On Fri, Oct 29, 2004 at 11:18:48PM +0200, stig erikson wrote:

i would like to log every single query coming in to the database into a
table. i would like the log to include the entire query and execution
time and execution cost, and if possible the user that executed the query.

A trigger is what i was thinking of, but how can i find out the actual
query, the time it took to execute it, etc.?

See the "Error Reporting and Logging" section of the documentation:

http://www.postgresql.org/docs/7.4/s...CONFIG-LOGGING

You might be able to feed the logging output to a script that inserts
into a table, but make sure that important log messages are also
stored outside the database to avoid losing them if trouble arises.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly