Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.

From: Richard Huxton <dev(at)archonet(dot)com>
To: Purusothaman A <purusothaman(dot)a(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.
Date: 2007-05-16 10:00:11
Message-ID: 464AD62B.9000003@archonet.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-general
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

In response to

Responses

pgsql-admin by date

Next:From: Joost KraaijeveldDate: 2007-05-16 12:36:45
Subject: pg_dump not enough space to create a backup FreeBSD 6.1?
Previous:From: Johann SpiesDate: 2007-05-16 08:47:26
Subject: Re: ERROR: invalid memory alloc request size

pgsql-general by date

Next:From: Jiří NěmecDate: 2007-05-16 13:11:17
Subject: Plpgsql function and variable substitute
Previous:From: Richard HuxtonDate: 2007-05-16 09:56:28
Subject: Re: Fixing broken permissions for deleted user

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group