From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Paul Tillotson <pntil(at)shentel(dot)net> |
Cc: | Madison Kelly <linux(at)alteeve(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Logging question |
Date: | 2005-01-18 04:20:59 |
Message-ID: | 20050118042059.GA15785@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 17, 2005 at 10:06:20PM -0500, Paul Tillotson wrote:
> I use ethereal (on the client--although it would possibly work on the
> server too) in such a case. It's a bit messy but if you just want to
> see what SQL statements were being run, then it works.
Caveats: sniffers like ethereal or tcpdump won't work over connections
that use local (Unix domain) sockets, and SSL connections might be
problematic.
> I also saw some where that the new version of ethereal has a dissector
> for Postgres, which would presumably show you the communication
> between the client and server in a nicely-formatted way.
Ethereal 0.10.8 appears to have a PostgreSQL dissector:
Request "create table foo (x integer);
Response CREATE TABLE
Request insert into foo values (1);
Response INSERT 0 1
Request insert into foo values (2);
Response INSERT 0 1
Request insert into foo values (3);
Response INSERT 0 1
Request select * from foo;
Response 1D 2D 3C SELECT
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-01-18 04:29:02 | Re: Logging question |
Previous Message | Hong Yuan | 2005-01-18 04:11:04 | Re: Multiline plpython procedure |