Skip site navigation (1)
Skip section navigation (2)
Hi all,
I am using Postgresql 8.2.
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?
Regards,
Purusothaman A
--
http://PurusothamanA.wordpress.com/
Peripheral Links
Header And Logo
|
Site Navigation
OIDs - file objects, are damaged by PostgreSQL.
- From: "Purusothaman A" <purusothaman(dot)a(at)gmail(dot)com>
- To: pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
- Subject: OIDs - file objects, are damaged by PostgreSQL.
- Date: Wed, 16 May 2007 11:12:01 +0530
Hi all,
I am using Postgresql 8.2.
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?
Regards,
Purusothaman A
--
http://PurusothamanA.wordpress.com/
- Follow-Ups:
- Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.
- From: Richard Huxton
- Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.
- Prev by Date: Re: How overcome wait for vacuum full?
- Next by Date: Re: ERROR: invalid memory alloc request size
- Previous by thread: How far does interrupting vacuum full rollback?
- Next by thread: Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.
- Indexes: