| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| 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 12:37:45 |
| Message-ID: | CAECtzeW8Go+S5GhGE5Xenk0rF8+0hVpEOceO7Tw6iLcqBqKCAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Le 20 nov. 2015 1:34 PM, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> a
écrit :
>
> 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?
>
If we do, we should already have done so because of the file size limit in
the tar format backup done with pg_dump.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sékine Coulibaly | 2015-11-20 15:57:50 | Re: Fwd: request |
| Previous Message | Alvaro Herrera | 2015-11-20 12:33:59 | Re: Confusing error message with too-large file in pg_basebackup |