Re: Confusing error message with too-large file in pg_basebackup - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Confusing error message with too-large file in pg_basebackup
Date
Msg-id 20151120184006.GP614468@alvherre.pgsql
Whole thread Raw
In response to Re: Confusing error message with too-large file in pg_basebackup  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: Confusing error message with too-large file in pg_basebackup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Guillaume Lelarge wrote:
> Le 20 nov. 2015 1:34 PM, "Alvaro Herrera" <alvherre@2ndquadrant.com> a
> écrit :

> > Hmm, so we let configure --with-segsize to change the file size.  The
> > configure help says that the limit should be "less than your OS' limit
> > on file size".  We don't warn them that this could cause backup
> > problems later on.  Should we add a blurb about that somewhere?
>
> If we do, we should already have done so because of the file size limit in
> the tar format backup done with pg_dump.

Agreed, please do.  I cannot lend you my time machine right now, though,
because I'm using it to go to a past conference I missed, so please ask
someone else.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13779: Inherited check constraint becomes non-inherited when related column is changed
Next
From: Tom Lane
Date:
Subject: Re: Confusing error message with too-large file in pg_basebackup