Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 45FDB9FB566 for ; Wed, 23 May 2007 05:34:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 34305-05 for ; Wed, 23 May 2007 05:34:14 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by postgresql.org (Postfix) with ESMTP id F078A9FB886 for ; Wed, 23 May 2007 05:34:16 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id i29so112244wxd for ; Wed, 23 May 2007 01:34:15 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=idaXOmk8fqUi3bIIxuL3vZHhcf7CsV9JN27ecZQ+0ZnmSzeZhaOf8WcUcm3br7qjknMtrOtqMAzKxBTtdo9KSU53kr45bPKcAPaoV1xa/5NH0JwjAsQ5XPuB+dsUQIqKlpuN0TNf0rYlmAWxRwIRRfWcT1pyBjPShKJJ9yQ9Qtk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=JEJK/FJ/jFWI5blAiAkk8/rY03ZP49EAZrwq5PCTTOglb1nIFjSOgiV6FABPP1paZ+chFE/RXjlIDZALtcaSSlo2myBkm/7mfaXXm8Ucv0Yarlq92VN0sjzPIaQIwhaAFdRnOHhD9J+/s130pYeZnjZyILOulJVfFs/1vIsad2E= Received: by 10.90.99.20 with SMTP id w20mr131634agb.1179909254877; Wed, 23 May 2007 01:34:14 -0700 (PDT) Received: by 10.90.86.9 with HTTP; Wed, 23 May 2007 01:34:09 -0700 (PDT) Message-ID: <3650d0d50705230134n15b993aat8bbc631836eef65e@mail.gmail.com> Date: Wed, 23 May 2007 14:04:09 +0530 From: "Purusothaman A" To: "Richard Huxton" Subject: Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL. Cc: pgsql-general@postgresql.org, pgsql-admin@postgresql.org In-Reply-To: <464AD62B.9000003@archonet.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_65849_12309523.1179909249806" References: <3650d0d50705152242y689c0ef8u56223ec15661c821@mail.gmail.com> <464AD62B.9000003@archonet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/234 X-Sequence-Number: 25554 ------=_Part_65849_12309523.1179909249806 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks Richard Huxton for your reply. I use client side api for uploading and downloading files. Its not happening immediately. But when database grows with data, file object got corrupted. My table structure is as follows. Table "public.conf" Column | Type | Modifiers --------+------------------------+----------- key | character varying(50) | not null value | character varying(100) | Indexes: "conf_pkey" PRIMARY KEY, btree ("key") Content of this table is, key | value ---------------------+-------- HX | 101800 MASK | 101801 Rockey4ND | 101802 Threshold | 60 Authentication Mode | 2 (5 rows) In the above, value of HX, MASK, Rockey4ND is 101800, 101801, 101802 (which was returned by lo_import()); Actually for some peculiar reason I kept "Value" field as var char instead of oid. (this could be reason?...) This problem occurs only few weeks after uploading files. Regards, Purusothaman A On 5/16/07, Richard Huxton wrote: > > Purusothaman A wrote: > > Hi all, > > > > I am using Postgresql 8.2. > > 8.2.which? > > > I am using client side api to upload/download files to/from postgresql > > using > > calls lo_export()/lo_import(); > > If I download a file from postgresql, few weeks later, files object's > > contents got damaged. > > > > I don't know why. > > > > Do any of you have encountered same problem? > > It's not impossible that PostgreSQL is corrupting your large-objects, > but it does seem unlikely. In what way were the large-object's contents > corrupted? Was the file-length the same? Do you know exactly when it got > corrupted? > > -- > Richard Huxton > Archonet Ltd > -- http://PurusothamanA.wordpress.com/ ------=_Part_65849_12309523.1179909249806 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks Richard Huxton for your reply.

I use client side api for uploading and downloading files.

Its not happening immediately. But when database grows with data, file object got corrupted.

My table structure is as follows.
             Table "public.conf"
 Column |          Type          | Modifiers
--------+------------------------+-----------
 key    | character varying(50)  | not null
 value  | character varying(100) |
Indexes:
    "conf_pkey" PRIMARY KEY, btree ("key")

Content of this table is,
         key         | value
---------------------+--------
 HX                  | 101800
 MASK                | 101801
 Rockey4ND           | 101802
 Threshold           | 60
 Authentication Mode | 2
(5 rows)

In the above, value of HX, MASK, Rockey4ND is 101800, 101801, 101802 (which was returned by lo_import());

Actually for some peculiar reason I  kept "Value" field as var char instead of oid. (this could be reason?...)

This problem occurs only few weeks after uploading files.

Regards,
Purusothaman A
 
On 5/16/07, Richard Huxton <dev@archonet.com> wrote:
Purusothaman A wrote:
> Hi all,
>
> I am using Postgresql 8.2.

8.2.which?

> I am using client side api to upload/download files to/from postgresql
> using
> calls lo_export()/lo_import();
> If I download a file from postgresql, few weeks later, files object's
> contents got damaged.
>
> I don't know why.
>
> Do any of you have encountered same problem?

It's not impossible that PostgreSQL is corrupting your large-objects,
but it does seem unlikely. In what way were the large-object's contents
corrupted? Was the file-length the same? Do you know exactly when it got
corrupted?

--
   Richard Huxton
   Archonet Ltd



--
http://PurusothamanA.wordpress.com/ ------=_Part_65849_12309523.1179909249806--