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

2007-05-24 Thread Richard Huxton
Purusothaman A wrote: Richard Huxton, In my system also its 2048 bytes chunk. The below output shows clearly that the last chunk differs in its length. You might have noticed in my previous mail that the string "\015\012\015\012" is missing some characters in SFRS2, SFRS1 and FASP_AVT database

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

2007-05-24 Thread Purusothaman A
Richard Huxton, In my system also its 2048 bytes chunk. The below output shows clearly that the last chunk differs in its length. You might have noticed in my previous mail that the string "\015\012\015\012" is missing some characters in SFRS2, SFRS1 and FASP_AVT database outputs. Have a look a

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

2007-05-23 Thread Richard Huxton
Purusothaman A wrote: Richard Huxton, Thanks for your detailed reply. I am maintaining various database of same kind in postgresql. Here I have shown various corrupted last line of output of select * from pg_largeobject where oid = xx; in 5 databases. I have used '\o e:\\filename.xml' befo

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

2007-05-23 Thread Purusothaman A
Richard Huxton, Thanks for your detailed reply. I am maintaining various database of same kind in postgresql. Here I have shown various corrupted last line of output of select * from pg_largeobject where oid = xx; in 5 databases. I have used '\o e:\\filename.xml' before executing query and

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

2007-05-23 Thread Richard Huxton
Purusothaman A wrote: Dear Richard Huxton, Thanks for your quick reply. only the first 3 values(HX, MASK, Rockey4ND) are file object's oid value. the other two are are not oid values. Umm - OK. Can I suggest perhaps having different tables for different types of data? I have shown origina

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

2007-05-23 Thread Purusothaman A
Dear Richard Huxton, Thanks for your quick reply. only the first 3 values(HX, MASK, Rockey4ND) are file object's oid value. the other two are are not oid values. I have shown original output values displayed by postgresql client. I can explain more. 1. HX is a XML file. after downloading that

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

2007-05-23 Thread Richard Huxton
Purusothaman A wrote: 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. Yes, but *HOW* - is it a different file, length is different, what? My table st

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

2007-05-23 Thread Purusothaman A
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 | Modif

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

2007-05-16 Thread Richard Huxton
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

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

2007-05-15 Thread Purusothaman A
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 probl