From: | "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | How to trace client sql requests? |
Date: | 2009-07-10 17:38:57 |
Message-ID: | 59259.216.185.71.24.1247247537.squirrel@webmail.harte-lyne.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a situation with a Rails project where test data in
mysteriously "disappearing" in the middle of a test run. I would
like to see the exact SQL of all client requests issued against a
single table during a fixed time span.
How can I best accomplish this in PostgreSQL?
#client_min_messages = notice
#log_min_messages = notice
#log_min_duration_statement = -1
...
#log_duration = off
Which of these, if any, should I alter; and to what? Am I
constrained to system wide logging or can this be enabled by
database?
Regards,
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB(at)Harte-Lyne(dot)ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-07-10 17:47:35 | Re: Overhead of union versus union all |
Previous Message | Jeff Davis | 2009-07-10 17:37:27 | Re: Overhead of union versus union all |