Upgrade from 7.3.4 to 7.4.6

[Cliff Reid]

Hello

Can anyone point me to or near the reason why my pg_dumpall of my 7.3.4 DB
and subsequent 7.4.6 psql restoration of that dump show up as a failure when
I run my programs against it. I am using libpq as the DB interface.
Program results are successful on the 7.3.4 system but I get seg-faults when
attempting to run on 7.4.6.

Recap: (7.3.4) pg_dumpall mydb > mydb_dump; (7.4.6) psql -f mydb_dump; all
seem to go as expected until I run program procedures againt the 7.4.6 DB.

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.

I hope this is enough info for a reasonable response.

Thanks

Clifford Reid




---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Tom Lane]

Post by Cliff Reid
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

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ***@postgresql.org)

[Cliff Reid]

Clifford Reid
Proximity Corporation
Vice President, Global Product Support
1065 Avenue of the Americas, 26th Floor
New York, New York 10018
Tel: [phone]
Fax: [phone]
Cell: 212-300-5639
***@proximitygroup.com


-----Original Message-----
From: Cliff Reid [mailto:***@proximitygroup.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: [phone]
Fax: [phone]
Cell: 212-300-5639

-----Original Message-----
Sent: Monday, November 01, 2004 12:20 PM
To: Cliff Reid
Subject: Re: [ADMIN] Upgrade from 7.3.4 to 7.4.6

Post by Cliff Reid
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

Post by Cliff Reid
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

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html