| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Karel Riveron Escobar <kescobar(at)estudiantes(dot)uci(dot)cu> |
| Cc: | Oscar Calderon <ocalderon(at)solucionesaplicativas(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Comunication protocol |
| Date: | 2013-05-17 16:22:54 |
| Message-ID: | CA+HiwqHerm071J7CRxPi3Ngt6wuxOcCeMwA6jcfz_b4HZmBpng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, May 18, 2013 at 1:03 AM, Karel Riveron Escobar
<kescobar(at)estudiantes(dot)uci(dot)cu> wrote:
>
> Thanks Oscar. I'm going to try your suggestion but I get a problem. I get the database server and apache server in the same PC because the system what I'm building is in development phase. Do you think that is a problem for wireshark?
>
>
From the documentation link that Tom provided you might have read that
the frontend/backend protocol which the database server and clients
connecting to it use - is a message based protocol in which the
messages are exchanged over either TCP/IP connection or UNIX doman
sockets. If you configure your client to use loopback interface
(127.0.0.1) to connect to the database you would be looking at a
TCP/IP connection, so probably manageable by Wireshark. Though, I
would suggest reading the protocol description in the documentation so
that you understand distinct phases of connection and subsequent
operation over the established connection.
--
Amit Langote
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Amiel | 2013-05-17 16:25:28 | Why does row estimation on nested loop make no sense to me |
| Previous Message | Karel Riveron Escobar | 2013-05-17 16:03:17 | Re: Comunication protocol |