From: | Alan Nilsson <anilsson(at)apple(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup failing |
Date: | 2014-01-15 20:10:27 |
Message-ID: | 58FE7FE8-DAF6-41AF-96B4-B2935071E80F@apple.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks all
alan
On Jan 15, 2014, at 6:30 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
>
>
> 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 | Torsten Förtsch | 2014-01-15 20:40:36 | Is http://www.postgresql.org/docs/9.3/static/row-estimation-examples.html up to date? |
Previous Message | Rémi Cura | 2014-01-15 18:20:37 | reading array[text] in C extension function |