pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Log query results?
3+ messages / 2 participants
[nested] [flat]

* Log query results?
@ 2004-02-11 02:49  Robert Creager <Robert_Creager@LogicalChaos.org>
  0 siblings, 1 reply; 3+ messages in thread

From: Robert Creager @ 2004-02-11 02:49 UTC (permalink / raw)
  To: pgsql-admin


Hey All,

I'm running 7.4.1 and am having problem when my app starts loading up on the
database.  I want to verify the data coming back from the queries is correct
from the server side (not application side), as then I'll be sure my app is
squirrelly (or the db is).

I don't see any options in postgresql.conf that would allow this, but was
wondering if any of the debug levels might get me what I want.  Or is there a
better way?

Thanks,
Rob

-- 
 19:43:51 up 2 days,  6:34,  3 users,  load average: 2.08, 2.17, 2.18

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Log query results?
@ 2004-02-11 06:03  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Robert Creager <Robert_Creager@LogicalChaos.org>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2004-02-11 06:03 UTC (permalink / raw)
  To: Robert Creager <Robert_Creager@LogicalChaos.org>; +Cc: pgsql-admin

Robert Creager <Robert_Creager@LogicalChaos.org> writes:
> I'm running 7.4.1 and am having problem when my app starts loading up on the
> database.  I want to verify the data coming back from the queries is correct
> from the server side (not application side), as then I'll be sure my app is
> squirrelly (or the db is).

> I don't see any options in postgresql.conf that would allow this, but was
> wondering if any of the debug levels might get me what I want.  Or is there a
> better way?

Nothing on the backend side that I can think of.  If you're using libpq
then you could use PQtrace, though that's really intended for debugging
libpq itself.  Or you could point a packet sniffer at the TCP
connection.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Log query results?
@ 2004-02-11 13:01  Robert Creager <Robert_Creager@LogicalChaos.org>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Robert Creager @ 2004-02-11 13:01 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin; Work <Robert_Creager@StorageTek.com>

When grilled further on (Wed, 11 Feb 2004 01:03:50 -0500),
Tom Lane <tgl@sss.pgh.pa.us> confessed:

> Robert Creager <Robert_Creager@LogicalChaos.org> writes:
> 
> Nothing on the backend side that I can think of.  If you're using libpq
> then you could use PQtrace, though that's really intended for debugging
> libpq itself.  Or you could point a packet sniffer at the TCP
> connection.
> 

Kind of what I thought.  Any (relatively) easy way to hack the
backend/re-compile to have it log the data (all the time)?

Thanks,
Rob

-- 
 05:53:30 up 2 days, 16:43,  3 users,  load average: 2.08, 2.20, 2.23

^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2004-02-11 13:01 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-02-11 02:49 Log query results? Robert Creager <Robert_Creager@LogicalChaos.org>
2004-02-11 06:03 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-02-11 13:01   ` Robert Creager <Robert_Creager@LogicalChaos.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox