Re: Logging broken messages

From: Steve Atkins <steve(at)blighty(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Logging broken messages
Date: 2017-02-07 20:05:00
Message-ID: 316B916B-0960-4473-944E-76DECDD47A9F@blighty.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> On Feb 6, 2017, at 9:21 AM, Rui Pacheco <rui(dot)pacheco(at)gmail(dot)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 message to the remote, it just hangs indefinitely. I suspect the problem could be on my side but I can’t find anything on my 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 up on syslog:

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

Cheers,
Steve

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-02-07 20:12:41 Re: Logging broken messages
Previous Message Steven Winfield 2017-02-07 13:20:36 Build exclusion constraints USING INDEX