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

From Rui Pacheco
Subject [GENERAL] Logging broken messages
Date
Msg-id 22DB2E08-6329-4EF8-B3E5-C0A7728A067B@gmail.com
Whole thread Raw
Responses Re: [GENERAL] Logging broken messages  (Steve Atkins <steve@blighty.com>)
Re: [GENERAL] Logging broken messages  (John DeSoi <desoi@pgedit.com>)
List pgsql-general
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:

postgres=# show log_destination
postgres-# ;
 log_destination 
-----------------
 syslog
(1 row)

postgres=# SET log_statement = 'all';
SET
postgres=# set log_min_messages = 'DEBUG5';
SET
postgres=# set log_min_error_statement = 'DEBUG5';
SET
postgres=# show syslog_ident;
 syslog_ident 
--------------
 postgres
(1 row)

postgres=# 


Many thanks,

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: [GENERAL] Result of timestamp - timestamp
Next
From: "Igal @ Lucee.org"
Date:
Subject: [GENERAL] BST Time Zone Discrepancy