From: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PGAdmin <pgsql-admin(at)postgresql(dot)org>, Work <Robert_Creager(at)StorageTek(dot)com> |
Subject: | Re: Log query results? |
Date: | 2004-02-11 13:01:04 |
Message-ID: | 20040211060104.50a3da7b.Robert_Creager@LogicalChaos.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
When grilled further on (Wed, 11 Feb 2004 01:03:50 -0500),
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> confessed:
> Robert Creager <Robert_Creager(at)LogicalChaos(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jodi Kanter | 2004-02-11 13:21:01 | constraints and performance |
Previous Message | Paulo Rogerio Zimolo | 2004-02-11 12:28:29 | Dumping from version 7.3.4 to 7.4.1 |