| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Confusing error message with too-large file in pg_basebackup |
| Date: | 2015-11-20 18:40:06 |
| Message-ID: | 20151120184006.GP614468@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Guillaume Lelarge wrote:
> Le 20 nov. 2015 1:34 PM, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-20 20:00:55 | Re: Confusing error message with too-large file in pg_basebackup |
| Previous Message | Tom Lane | 2015-11-20 17:01:28 | Re: [BUGS] BUG #13779: Inherited check constraint becomes non-inherited when related column is changed |