| 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>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Confusing error message with too-large file in pg_basebackup |
| Date: | 2015-11-20 12:33:59 |
| Message-ID: | 20151120123359.GO614468@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Guillaume Lelarge wrote:
> Looking at the file's size is probably a better idea. As far as I know,
> PostgreSQL doesn't create files bigger than 1GB, except for log files. I'm
> not sure about this but I guess pg_basebackup doesn't ship log files. So,
> looking at the size would work.
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?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2015-11-20 12:37:45 | Re: Confusing error message with too-large file in pg_basebackup |
| Previous Message | Michael Paquier | 2015-11-20 12:09:41 | Re: Confusing error message with too-large file in pg_basebackup |