From: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
---|---|
To: | Israel Ben Guilherme Fonseca <israel(dot)bgf(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Incoming/Sent traffic data |
Date: | 2011-05-12 16:40:00 |
Message-ID: | BANLkTimsypLk7AhogY10vHQYBp=6wEGS9w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> About the log, i'm using log_statement = "all", on the postgres config,is there any
> other specific option?
You could try setting log_min_messages = debug1 (I don't think
anything below that--i.e., debug2 through debug5--is useful for your
case, but you can give it a shot to see what's there).
> My current implementation of proxy just use sockets to transmit the data between the app (that's
> why the port 4444 on connections) to the database, that's how I check the size of data
> transfered with it (it have a GUI to clear the traffic so I can check only the operation, not the
> setup).
Nice. I didn't mean to imply you were entirely unscientific about
this, just that you should be careful regarding assumptions as to what
is sent where when. A tool like Wireshark is (relatively) easy to pick
up and gives you tremendous insight into what's going on on the wire
with no application changes required (and it even has a PostgreSQL
protocol plugin by default so you don't need to stare at raw bytes).
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com
From | Date | Subject | |
---|---|---|---|
Next Message | Israel Ben Guilherme Fonseca | 2011-05-12 17:27:06 | Re: Incoming/Sent traffic data |
Previous Message | Israel Ben Guilherme Fonseca | 2011-05-12 11:32:13 | Re: Incoming/Sent traffic data |