FW: Upgrade from 7.3.4 to 7.4.6

Clifford Reid
Proximity Corporation
Vice President, Global Product Support
1065 Avenue of the Americas, 26th Floor
New York, New York 10018
Tel: 646-452-5820
Fax: 646-452-5821
Cell: 212-300-5639
creid(at)proximitygroup(dot)com

-----Original Message-----
From: Cliff Reid [mailto:creid(at)proximitygroup(dot)com]
Sent: Monday, November 01, 2004 12:27 PM
To: 'Tom Lane'
Subject: RE: [ADMIN] Upgrade from 7.3.4 to 7.4.6

Tom

Thanks for the reply, much appreciated. On-the-wire is a step in the right
direction. To get a bit more out of you regarding this issue, what exactly
is the correct method for receiving proper data representation? Is there a
play that I can use with the existing PG utilities and/or SQL statements?

Best regards,

Clifford Reid
Proximity Corporation
Vice President, Global Product Support
1065 Avenue of the Americas, 26th Floor
New York, New York 10018
Tel: 646-452-5820
Fax: 646-452-5821
Cell: 212-300-5639
creid(at)proximitygroup(dot)com

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Monday, November 01, 2004 12:20 PM
> To: Cliff Reid
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] Upgrade from 7.3.4 to 7.4.6
>
> "Cliff Reid" <creid(at)proximitygroup(dot)com> writes:
> > My instant analysis: It seems to not like BINARY CURSOR. When I remove
> > BINARY from the SQL DECLARE string, I no longer receive the seg-fault
> but
> > the data results (presentation) are not as expected.
>
> 7.4 changed the external representation in which BINARY CURSOR results
> are delivered. Before 7.4 you got the (very machine- and even version-
> dependent) server internal representation; now you get an on-the-wire
> representation that we hope to keep stable.
>
> regards, tom lane