Re: Large object corruption during 'piped' pg_restore - Mailing list pgsql-general

From Bosco Rama
Subject Re: Large object corruption during 'piped' pg_restore
Date
Msg-id 4D39C5F5.1090609@boscorama.com
Whole thread Raw
In response to Re: Large object corruption during 'piped' pg_restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Large object corruption during 'piped' pg_restore  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-general
Tom Lane wrote:
>
> So I'm not sure whether to fix it, or leave it as a known failure case
> in old branches.  Comments?

I understand the reluctance to fool with stable code.  I have zero insight
into your installed versions distribution and backward compatibility needs
so any comment I may have here is purely selfish.

As an end user there is one area of the DB that I want to work correctly
100% of the time and that is the dump/restore tool(s).  If it's not going
to work under certain circumstances it should at least tell me so and
fail.  I don't think having the tool appear to work while corrupting the
data (even if documented as doing so) is a viable method of operation.

Just my $0.02

Bosco.

pgsql-general by date:

Previous
From: tuanhoanganh
Date:
Subject: Re: PostgreSQL 9.0.1 PITR can not copy WAL file
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Large object corruption during 'piped' pg_restore