Re: 3.0 fe/be protocol bug?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John DeSoi <jd(at)icx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 3.0 fe/be protocol bug?
Date: 2003-05-28 23:56:33
Message-ID: 9294.1054166193@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

John DeSoi <jd(at)icx(dot)net> writes:
> I'm working on a new client with the 3.0 protocol. I'm having a problem
> with the data DataRow message from this select:

> select oid, datconfig from pg_database

> There seems to be a problem with text[] type for datconfig. The hex
> dump (from tcpflow) for 1 data row message is:

> 44 0000 0013 0002 0000 0005 3137303632 FFFF FFFF
> D mesg len 2col col1 len5 oid 17602 len col2 here?

Looks fine to me. -1 length means a NULL.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2003-05-29 02:19:19 PostgreSQL RPM's and Red Hat.
Previous Message Tom Lane 2003-05-28 23:55:11 Re: Mismatched parentheses when creating a rule with multiple action queries