On Jul 10, 2009, at 7:38 PM, James B. Byrne wrote:
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.
Are you sure
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 =
On Fri, Jul 10, 2009 at 01:38:57PM -0400, James B. Byrne wrote:
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.
On Fri, July 10, 2009 14:58, hubert depesz lubaczewski wrote:
You can enable by database:
alter database x set log_min_duration_statement = 0;
Many, many thanks. Now of course I need more help...
The situation is that data inserted into the DB is not being found
on a subsequent select and
On Fri, July 10, 2009 16:10, hubert depesz lubaczewski wrote:
truncate. but first simple question - did you commit the inserts?
But if it were done with truncate then I would see truncate in the
log file, yes?
Second, I am working with PG through an ORM called ActiveRecord,
part of the
On Fri, Jul 10, 2009 at 03:45:35PM -0400, James B. Byrne wrote:
I believe that this is what I want to examine. Is there a server
side technique that I can use which will tell me what data this
statement returned or if it found nothing?
not really, sorry.
In any case, I see the INSERTS and I
On Jul 10, 2009, at 1:31 PM, James B. Byrne wrote:
On Fri, July 10, 2009 16:10, hubert depesz lubaczewski wrote:
truncate. but first simple question - did you commit the inserts?
But if it were done with truncate then I would see truncate in the
log file, yes?
Second, I am working
