Postgres Pro
Downloads
Home   >   mailing lists

Thread: BUG #3399: Compatibility issue of the bytea field type

BUG #3399: Compatibility issue of the bytea field type

From
"Bing Xia"
Date:
The following bug has been logged online:

Bug reference:      3399
Logged by:          Bing Xia
Email address:      bxia@alpha.ipswitch.com
PostgreSQL version: 8.2.4
Operating system:   MS Windows Serve 2003 Standard Edition SP1
Description:        Compatibility issue of the bytea field type
Details:

We use PostgreSQL 8.1.x as our server backend DB. In one table, we store all
the certificates. The data type for the certificates is bytea. Everything
works fine. However, after we upgrade to PostgreSQL 8.2.4. as we use the
exact same code to query the certificates, we only retrieve the part of the
certificates. It seems that the resultant certificates are never bigger than
256 bytes.

Since we have not changed anything in the data access layer except the
PostgreSQL upgrade, we think it could be a defect in the latest PostgreSQL.


Thanks for any feedback.

Bing

Re: BUG #3399: Compatibility issue of the bytea field type

From
Tom Lane
Date:
"Bing Xia" <bxia@alpha.ipswitch.com> writes:
> We use PostgreSQL 8.1.x as our server backend DB. In one table, we store all
> the certificates. The data type for the certificates is bytea. Everything
> works fine. However, after we upgrade to PostgreSQL 8.2.4. as we use the
> exact same code to query the certificates, we only retrieve the part of the
> certificates. It seems that the resultant certificates are never bigger than
> 256 bytes.

> Since we have not changed anything in the data access layer except the
> PostgreSQL upgrade, we think it could be a defect in the latest PostgreSQL.

If you want anyone to take this seriously, you need to provide a test case.

            regards, tom lane