Philip Warner wrote: > At 05:50 PM 23/10/2002 -0400, Bruce Momjian wrote: > >Looking at the pg_dump code, it seems the fseeks are optional in there > >anyway because it already has code to read the file sequentially rather > > But there are features that are not available if it can't seek: eg. it will > not restore in a different order to that in which it was written; it will > not dump data offsets in the TOC so dump files can not be restored in > alternate orders; restore times will be large for a single table (it has to > read the entire file potentially).
OK, that helps. We just got a list of 2 other OS's without fseeko and with large file support. Any NetBSD before Auguest 2002 has that problem. We are going to need to either get fseeko workarounds for those, or disable those features in a meaningful way. -- 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 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
