Received: from nsi.edu (amethea.nsi.edu [198.133.185.9]) by hub.org (8.8.8/8.7.5) with ESMTP id OAA06118 for ; Fri, 4 Sep 1998 14:37:21 -0400 (EDT) Received: from nsi.edu (IDENT:reina@bigred.nsi.edu [204.128.156.214]) by nsi.edu (8.9.1/8.9.1) with ESMTP id LAA07649; Fri, 4 Sep 1998 11:37:18 -0700 (PDT) Sender: reina@nsi.edu Message-ID: <35F033B5.BD8C2F01@nsi.edu> Date: Fri, 04 Sep 1998 11:38:45 -0700 From: "G. Anthony Reina" Organization: The Neurosciences Institute X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.34 i686) MIME-Version: 1.0 To: reina@nsi.edu, "pgsql-questions@postgresql.org" Subject: DECLARE BINARY CURSOR problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We recently moved from using an SGI under IRIX 6.2 to a Pentium II running RedHat Linux as our database postmaster. For some reason, declaring a binary cursor gives erroneous data now. We think that this may be because one uses big-endian and the other little-endian for memory. Has anyone had any experience with this problem? Is there a way to specify which way to pass the binary cursor (big or little-endian) as the output memory? Thanks. -Tony Reina