| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Alan Nilsson <anilsson(at)apple(dot)com> |
| Subject: | Re: pg_basebackup failing |
| Date: | 2014-01-15 11:19:56 |
| Message-ID: | CABUevEzoihrGkFOYnMde5NxDhXfA+mnJd5jr-5mjKs7XLdRDhA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jan 15, 2014 12:07 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?
>
Yeah, how did you actually end up with a file that size? Do you have any
non standard compiler options set when you built your server?
/Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2014-01-15 11:36:24 | Re: how is text-equality handled in postgresql? |
| Previous Message | Sameer Kumar | 2014-01-15 11:05:58 | Re: pg_basebackup failing |