pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Huxton <dev@archonet.com>
To: Purusothaman A <purusothaman.a@gmail.com>
Cc: pgsql-general@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.
Date: Thu, 24 May 2007 07:41:55 +0100
Message-ID: <465533B3.5060704@archonet.com> (raw)
In-Reply-To: <3650d0d50705232254w265b94b0yaaf5163b92567403@mail.gmail.com>
References: <3650d0d50705152242y689c0ef8u56223ec15661c821@mail.gmail.com>
	<464AD62B.9000003@archonet.com>
	<3650d0d50705230134n15b993aat8bbc631836eef65e@mail.gmail.com>
	<46540766.2030108@archonet.com>
	<3650d0d50705230756g5fdf8bdava3de463eb6f82ad9@mail.gmail.com>
	<4654621C.8010700@archonet.com>
	<3650d0d50705232254w265b94b0yaaf5163b92567403@mail.gmail.com>

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 = xxxxxx; in 5 databases.
> 
> I have used '\o e:\\filename.xml' before executing query and inspected the
> output in that file.
> 
> Kindly look at the end of line in all 5 outputs.
> First 3 output shows few missing characters.
> But last 2 output is the perfect one.
> 
> 1. Output of SFRS2 database:
> 2. Output of SFRS1 database:
 > 3. Output of FASP_AVT database:

Let's have a look at the last few bytes of these three rows. For 
example, below is a very short file that finishes with "end<NL>".

SELECT loid,pageno,length(data),encode(data, 'hex') FROM pg_largeobject 
WHERE loid=340161 AND pageno=0;
   loid  | pageno | length |                             encode
--------+--------+--------+----------------------------------------------------------------
  340161 |      0 |     31 | 
54686973206973206120746573742066696c650a6c696e6520320a656e640a
(1 row)


It doesn't seem to be random garbage at the end of your rows, so lets 
see what it is.

Oh - things we can rule out:
1. Index corruption. We're not missing the last row.

Adding the length check above will show us if the row is truncated or 
full of spaces.

-- 
   Richard Huxton
   Archonet Ltd



view thread (10+ messages)  latest in thread

Message-ID: <465533B3.5060704@archonet.com>
Permalink:  ../465533B3.5060704@archonet.com/
Also on:    postgresql.org/message-id/465533B3.5060704@archonet.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: dev@archonet.com, purusothaman.a@gmail.com, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] OIDs - file objects, are damaged by PostgreSQL.
  In-Reply-To: <465533B3.5060704@archonet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox