| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
| Cc: | Alan Nilsson <anilsson(at)apple(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup failing |
| Date: | 2014-01-15 14:30:34 |
| Message-ID: | CAB7nPqQRNLYfymgyCF=4UwADRcf8rEX-m=Kq7FSfVTHePajFvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 15, 2014 at 8:05 PM, Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>wrote:
> The error you are seeing is triggered because this relation file
>> exceeds MAX_TAR_MEMBER_FILELEN or 8GB for a single tar member, which
>> is as well the norm for tar.
>
>
> I thought PostgreSQL would break the file if it grows beyond 1GB (1GB is
> segment size which one can modify while compiling). Am I missing something
> or have I got it totally wrong?
>
No, you are missing nothing. Thanks for reminding :) (This is settable with
./configure --with-segsize)
So the build has been done with some uncommon option.
Regards,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-15 14:43:40 | Re: how is text-equality handled in postgresql? |
| Previous Message | Amit Langote | 2014-01-15 14:15:51 | Re: pg_depend OBJID not found |