| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Giles Lean" <giles(at)nemeton(dot)com(dot)au> |
| Subject: | Re: pg_dump and large files - is this a problem? |
| Date: | 2002-10-24 09:23:13 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961ED2@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The question is *which* seek APIs we need to support. Are there any
> besides fseeko() and fgetpos()?
On AIX we have
int fseeko64 (FILE* Stream, off64_t Offset, int Whence);
which is intended for large file access for programs that do NOT
#define _LARGE_FILES
It is functionality that is available if _LARGE_FILE_API is defined,
which is the default if _LARGE_FILES is not defined.
That would have been my preferred way of handling large files on AIX
in the two/three? places that need it (pg_dump/restore, psql and backend COPY).
This would have had the advantage that off_t is not 64 bit in all other places
where it is actually not needed, no ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hosen, John | 2002-10-24 12:19:02 | Re: 'epoch'::timestamp and Daylight Savings |
| Previous Message | Luis Alberto Amigo Navarro | 2002-10-24 08:24:01 | Re: crashes with postgresql 7.2.1 on IRIX 6.5 |