Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XPds4-0001Lr-73 for pgsql-general@arkaria.postgresql.org; Thu, 04 Sep 2014 20:43:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XPds3-0001sq-Ia for pgsql-general@arkaria.postgresql.org; Thu, 04 Sep 2014 20:43:07 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XPds1-0001sa-VI for pgsql-general@postgresql.org; Thu, 04 Sep 2014 20:43:06 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XPdry-0003bC-7Q for pgsql-general@postgresql.org; Thu, 04 Sep 2014 20:43:03 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by gateway2.nyi.internal (Postfix) with ESMTP id D6D0C20A0B for ; Thu, 4 Sep 2014 16:42:59 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 04 Sep 2014 16:42:59 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=dmrRTMoOpwOYYw3ZQHv2VQVGJJ0=; b=lV/0UdzHRKaYr0KAMj7j9QpMIRWW Li+02mcC4uOD5zLD/T3Q7QpmWHyx10HDAGQeJQPvmp0J1ftzDUmxPoSGXHJb5jGY oveYLh0Zi0HKgFtXJjf4V4luas2ACgo3wj1ajeQ029TLrajvB9AzJ1AM1/GLTvuD YKwv3Lqpj28XHBI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=dmrRTMoOpwOYYw3ZQHv2VQ VGJJ0=; b=EJLf84YoLAccmn+KRuTt+rxsv/D2J6mxMqnZRJ5NIyxvB1PLavqbyT mKdXfTIXaDRjDqsR1JkUrMidHP5ijbLV8hxi8xOclVKXlhqBS4Rhsv/0ZQzTfaft ous61zyLp6MKkkepxTYOSy8hMDPud9xeFPeVf4OFBnIbqB5yv2J6M= X-Sasl-enc: /zTcdIxjYaKyWYk/+gHWylOwSGUJM0a2aANavT4PF3RM 1409863379 Received: from killi.site (unknown [24.17.179.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 3752FC00915; Thu, 4 Sep 2014 16:42:59 -0400 (EDT) Message-ID: <5408CED2.10302@aklaver.com> Date: Thu, 04 Sep 2014 13:42:58 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Alanoly Andrews , 'Craig James' CC: "pgsql-admin@postgresql.org" , "pgsql-general@postgresql.org" Subject: Re: Re: [ADMIN] Cannot retrieve images inserted through VB and odbc, after a table reorganization. References: <6909b219ecae4d41b431efdaf6c953a3@Exch2.invera.com> <5407679B.2030906@aklaver.com> <54086B77.9090102@aklaver.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 09/04/2014 08:03 AM, Alanoly Andrews wrote: > Thanks, Adrian for the response. > > Yes, we are using the "large object" as per the specifications in the > special "lo" module that we installed on the backend server. The table > is created using the "lo" datatype for the image field and the table is > being regularly used for insertions and retrievals using utilities other > than ones using odbc. The odbc connection, too, works well on the table, > as long as the table data is not reorganized after insertion(s). > > Here are three pages of our postgres odbc driver settings. Sorry, they > are screen captures, not plain text! Hmm, to me at least nothing seems out of place. Though to be honest I am not sure what 'Bytea as LO' does in this situation. Are you actually trying to store any large objects in bytea columns? I searched on the error message you originally posted, but is fairly generic and covers a lot of different error sources. So, is there any more specific error information in either the Postgres or ODBC logs? > > Alanoly. -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general