Thanks all
alan
On Jan 15, 2014, at 6:30 AM, Michael Paquier wrote:
>
>
>
> On Wed, Jan 15, 2014 at 8:05 PM, Sameer Kumar 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 fo
On Wed, Jan 15, 2014 at 8:05 PM, Sameer Kumar 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 (1G
On Jan 15, 2014 12:07 PM, "Sameer Kumar" 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
>
> 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). A
On Wed, Jan 15, 2014 at 6:53 AM, Alan Nilsson wrote:
> Could someone give me some insight to the following error message:
>
> [mqsql06:/Volumes/SQL_Set] _postgres% pg_basebackup --user=replicate
> --host=mqsql03 -xP -Fp --pgdata=pgsql
> 19439890/65873894 kB (29%), 1/1 tablespace
> pg_basebackup: c
Could someone give me some insight to the following error message:
[mqsql06:/Volumes/SQL_Set] _postgres% pg_basebackup --user=replicate
--host=mqsql03 -xP -Fp --pgdata=pgsql
19439890/65873894 kB (29%), 1/1 tablespace
pg_basebackup: could not get transaction log end position from server: ERROR:
