Re: Large object corruption

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Large object corruption
Date: 2003-05-02 21:22:41
Message-ID: 2673.1051910561@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> A client of mine has claimed to encounter the following:
> When they have an unexpected power-out, large objects written to the database
> but not checkpointed (i.e. in the middle of a transaction, and later than the
> checkpoint interval) will be corrupted, and not even the previous version of
> the LO is retrieveable.

Not a known issue, and not a very credible report either. LOs use the
same transaction mechanisms as everything else.

Is this the same client that apparently lost an index to a filesystem
failure earlier today? I wonder just how extensive that failure was...
you might try looking for zeroed pages in pg_largeobject and its
index...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-05-02 21:36:55 Re: Bug #963: Weird plpython trigger(?) behaviour in 7.3.2
Previous Message Josh Berkus 2003-05-02 20:02:03 Large object corruption