Re: Issues with restoring

From: "beer" <beer(at)cmu(dot)edu>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Issues with restoring
Date: 2006-03-28 15:14:37
Message-ID: 1204.128.237.251.59.1143558877.squirrel@128.237.251.59
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom

Dont think its large file support, I'm running on FC4, the problem existed on FC1 too.

I'll try the custom format and see if that helps. Thanks for the recommendation.

-bill

On Mon, March 27, 2006 4:35 pm, Tom Lane said:
> "beer" <beer(at)cmu(dot)edu> writes:
>> We have a medium sized database that when dumped creates +4G files
>> within the tar archive. When we restore it seems that pg_restore has a
>> 4G limit for reading files, once it reads 4G of a file, it moves on to
>> the next file. Has anyone else experienced this problem?
>
> There is a member size limit inherent to the tar-archive code, although I
> thought it was 8G not 4G. I'd recommend using custom format (-Fc not
> -Ft).
>
> Still, if the thing is truncating your data and not telling you so, that'd
> qualify as a bug.
>
> On some platforms there might be a problem with lack of large-file support
> at the stdio level, too. What is your platform?
>
> regards, tom lane
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Seneca Cunningham 2006-03-28 15:22:47 Re: More AIX 5.3 fun - out of memory ?
Previous Message Tom Lane 2006-03-28 15:07:35 Re: [GENERAL] PANIC: heap_update_redo: no block