Re: [GENERAL] Logging broken messages - Mailing list pgsql-general

From Steve Atkins
Subject Re: [GENERAL] Logging broken messages
Date
Msg-id 316B916B-0960-4473-944E-76DECDD47A9F@blighty.com
Whole thread Raw
In response to [GENERAL] Logging broken messages  (Rui Pacheco <rui.pacheco@gmail.com>)
Responses Re: [GENERAL] Logging broken messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> On Feb 6, 2017, at 9:21 AM, Rui Pacheco <rui.pacheco@gmail.com> wrote:
>
> Hello,
>
> I’m trying to implement a version of the wire protocol but I’ve hit a problem: whenever I send a Close Statement
messageto the remote, it just hangs indefinitely. I suspect the problem could be on my side but I can’t find anything
onmy code that doesn’t match the manual. 
>
> Is there a way to configure Postgres to debug this? I’ve tried setting a number of log parameters but nothing shows
upon syslog: 

Wireshark has a v3 postgresql protocol dissector. It might be worth comparing your code with libpq and see if anything
looksdifferent. 

Cheers,
  Steve



pgsql-general by date:

Previous
From: Steven Winfield
Date:
Subject: [GENERAL] Build exclusion constraints USING INDEX
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Logging broken messages