Re: Tracing used SQL statments

In your postgresql.conf file (on my system this is /etc/postgresql.conf -
don't know how standard that is) insert the following line:

debug_print_query = on

then restart the postmaster (again, on my system: /etc/init.d/postgresql
restart) and you'll be on your way. It ends up in the general
postgres.log, /var/log/postgres.log on my system.

ap

----------------------------------------------------------------------
Andrew J Perrin - http://www.unc.edu/~aperrin
Assistant Professor of Sociology, U of North Carolina, Chapel Hill
clists@perrin.socsci.unc.edu * andrew_perrin (at) unc.edu


On Wed, 25 Jun 2003, Matthew Pinhorn wrote:

>
> Hello,
>
>     I am wondering if somebody can help me. I want to know if there is a
> way that I can make some kind of a log file of all of the SQL statements that
> are used in my database. It was suggested to make that I could make a trace
> of them and I am not sure how to do that.
>
>     I have inherited a database from a former co-worker and now I am
> starting to get crashes. The crashes has SET TRANSACTION ISOLATION LEVEL
> messages in the log file. So I think that there is a lock on the database.
>  And if I can see the queries that are causing the crash I might be able
> to fix the problem.
>
> Thanks
>
> Matthew
>
> --
> Matthew Pinhorn                         E-Mail: mailto:matthew.pinhorn@iona.com
> IONA                                     WWW:    http://www.orbacus.com
> Making Software Work Together (tm)       Phone:  (709) 738-3725 x 10
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org
>