Re: How to trace client sql requests?

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: James B(dot) Byrne <byrnejb(at)harte-lyne(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to trace client sql requests?
Date: 2009-07-11 09:54:15
Message-ID: 215D5260-3D98-4CFF-A5BA-50C7A8504E3A@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 you're looking at that data from the same connection, or
if not, that the inserts get committed? I've seen data "disappear" if
people forgot they were in a transaction block and didn't commit at
the end.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.

!DSPAM:737,4a58614910131561119940!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Raymond O'Donnell 2009-07-11 14:03:24 Re: Question
Previous Message Alban Hertroys 2009-07-11 09:35:06 Re: Best practices to WorkFlow design?