Re: pg_restore fails with a custom backup file - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_restore fails with a custom backup file
Date
Msg-id 200612181645.kBIGjUV16383@momjian.us
Whole thread Raw
In response to Re: pg_restore fails with a custom backup file  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_restore fails with a custom backup file
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Magnus Hagander wrote:
> >> A question though - is there any *gain* from using 64-bit offsets in the
> >> actual backend? The change could of course be done in port.h, but that
> 
> > No, not really.  All files are kept < 1gig for the backend.
> 
> Not so: consider a backend COPY reading or writing a multi-gig table.
> This will fail if the platform hasn't got largefile support.

Good point --- but do we do any seeks in COPY files?  I don't think so,
so I don't see how we would benefit from large file support there. 
Certainly people are dumping >2 gig files.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Dirty pages in freelist cause WAL stuck
Next
From: Tom Lane
Date:
Subject: Re: Operator class group proposal