From: Robert Creager <Robert_Creager@LogicalChaos.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PGAdmin <pgsql-admin@postgresql.org>
Cc: Work <Robert_Creager@StorageTek.com>
Subject: Re: Log query results?
Date: Wed, 11 Feb 2004 06:01:04 -0700
Message-ID: <20040211060104.50a3da7b.Robert_Creager@LogicalChaos.org> (raw)
In-Reply-To: <15682.1076479430@sss.pgh.pa.us>
References: <20040210194904.4293fb8a.Robert_Creager@LogicalChaos.org>
<15682.1076479430@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: Robert_Creager@LogicalChaos.org, tgl@sss.pgh.pa.us, Robert_Creager@StorageTek.com
Subject: Re: Log query results?
In-Reply-To: <20040211060104.50a3da7b.Robert_Creager@LogicalChaos.org>
References: <20040210194904.4293fb8a.Robert_Creager@LogicalChaos.org> <15682.1076479430@sss.pgh.pa.us> <20040211060104.50a3da7b.Robert_Creager@LogicalChaos.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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