Re: Confusing error message with too-large file in pg_basebackup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Gould <daveg(at)sonic(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Confusing error message with too-large file in pg_basebackup
Date: 2015-11-21 01:54:50
Message-ID: 9732.1448070890@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Gould <daveg(at)sonic(dot)net> writes:
> My vote would be that it should go in 9.5. If it gets back patched then
> some dumps produced by 9.4.x would not be readable by 9.4.x-1. But no 9.5.x
> dump is broken by changing it now.

The thing is, though, that without the patch 9.4.x would have failed to
produce such a dump at all. Is that really a better outcome? At least
if you have the dump, you have the option to update so you can read it.
With no dump at all, you might be screwed at a most inopportune moment.
(Think "automatic dump script was failing and nobody noticed" ...)

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2015-11-21 05:16:56 Re: Confusing error message with too-large file in pg_basebackup
Previous Message David Gould 2015-11-21 01:14:50 Re: Confusing error message with too-large file in pg_basebackup