The answers are great, thanks!
> On 9 Feb 2017, at 20:26, Andres Freund wrote:
>
> On 2017-02-09 20:17:33 +0100, Rui Pacheco wrote:
>> I’ve been anxiously waiting for that reply but got nothing. I even mailed
>> the mailing list manager again with no reply. And when I click on that link
>> I g
On 2017-02-09 20:17:33 +0100, Rui Pacheco wrote:
> I’ve been anxiously waiting for that reply but got nothing. I even mailed the
> mailing list manager again with no reply. And when I click on that link I get
> a server error: "An internal server error occurred.”
The server error has already bee
I’ve been anxiously waiting for that reply but got nothing. I even mailed the
mailing list manager again with no reply. And when I click on that link I get a
server error: "An internal server error occurred.”
But thanks, this helps me focus on the problem.
> On 9 Feb 2017, at 20:15, Tom Lane w
Rui Pacheco writes:
> I’ve sent a similar email to the general mailing list but got no reply.
Uh, multiple people answered you, see
https://www.postgresql.org/message-id/flat/22DB2E08-6329-4EF8-B3E5-C0A7728A067B%40gmail.com
> Is there a way to see how Postgres parses the message? I’ve set loggin
2017-02-09 20:12 GMT+01:00 Rui Pacheco :
> Not sure this solves my problem. I’d like to debug how the server is
> failing to parse my message, not what it looks like on the wire. I am the
> one forming the message after all.
>
> My apologies if I missed something.
>
>
ok
no problem
Regards
Pave
Not sure this solves my problem. I’d like to debug how the server is failing to
parse my message, not what it looks like on the wire. I am the one forming the
message after all.
My apologies if I missed something.
> On 9 Feb 2017, at 20:05, Pavel Stehule wrote:
>
> Hi
>
> 2017-02-09 20:01 GM
Hi
2017-02-09 20:01 GMT+01:00 Rui Pacheco :
> Hello,
>
> I’ve sent a similar email to the general mailing list but got no reply.
>
> I’m trying to write my own implementation of the wire protocol. I’m stuck
> at the Parse message where I send it to the server but always get the
> following error: