Re: [HACKERS] vlen in libpq using user defined data type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Hartwig <daveh(at)insightdist(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] vlen in libpq using user defined data type
Date: 1998-09-10 14:25:52
Message-ID: 6821.905437552@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Hartwig <daveh(at)insightdist(dot)com> writes:
> Anyway, as pqlib reads the string sent to it by the backend (a la psql),
> it must first read the length of each string. The problem is that the
> length of the string for accntnum in some outrageously large number
> which ultimately hangs psql. BTW, atttypemod = -1 and typlen = 4 in
> the FE.

Is this fixed by the patch I sent in last night? Your description does
not sound like what I would expect. The bug I fixed was that PQfsize()
would return 65535 instead of -1 for a varlen field. But neither libpq
nor psql make use of that value (which is why I hadn't noticed it was
broken). Are you using some other frontend code that does depend on
PQfsize to return the right thing?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-09-10 15:09:38 Re: [HACKERS] fix for libpq choking on varlen fields
Previous Message Bruce Momjian 1998-09-10 14:25:32 Re: [HACKERS] open 6.4 items