Re: Large object corruption during 'piped' pg_restore

From: Bosco Rama <postgres(at)boscorama(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Large object corruption during 'piped' pg_restore
Date: 2011-01-20 22:07:01
Message-ID: 4D38B205.6050606@boscorama.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hi Tom,

Tom Lane wrote:
> Bosco Rama <postgres(at)boscorama(dot)com> writes:
>> We've discovered (or possibly rediscovered?) a corruption when restoring large
>> objects.
>
>> If 'standard_conforming_strings = on' is set in our DB (which is required for
>> our app) then the piped restore method (e.g. pg_restore -O backup.dat | psql)
>> results in the large objects being corrupted.
>
> This vaguely reminds me of some long-since-fixed bug, but since you have
> neglected to give any version details, it's hard to say for sure.
> What PG version was the original server? The pg_dump you used to make
> the backup? The pg_restore? The target server?

Yeah, I only realized I hadn't added that as I saw it being sent. :-(

All servers and client tools involved are PG 8.4.6 on Ubuntu Server 10.04.1 LTS
with all current updates applied.

The dump file was made using: pg_dump -Fc -Z1 > backup.dat

Bosco.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-01-20 23:14:57 Re: Large object corruption during 'piped' pg_restore
Previous Message Tom Lane 2011-01-20 21:41:45 Re: Large object corruption during 'piped' pg_restore

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-01-20 22:09:16 Re: SSI and Hot Standby
Previous Message Tomas Vondra 2011-01-20 21:58:00 Re: estimating # of distinct values