Peter Eisentraut wrote: > Bruce Momjian writes: > > > My point is that it seems fsetpos is the approved way of accessing large > > files, rather than fseeko. In fact, I don't have fseeko here but I do > > have fsetpos, and it does handle large files because my includes have > > this: > > > > typedef off_t fpos_t > > typedef quad_t off_t; > > Interesting. In general, you can't rely on fpos_t being an integral type, > which indeed on my machine it isn't. But for pg_dump we need an integral > type because we do offset arithmetic.
Oh, is that why fsetpos is always SEEK_SET and not SET_CURR or offset stuff. Strange I don't have fseeko and do have large file support. BSD/OS has had it for years. I guess they just do off_t arithmetic, but that isn't portable. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
