At 09:36 PM 23/10/2002 -0400, Bruce Momjian wrote:
????? if we have not got a 64 bit seek function of any kind, then use a 32 bit seek - the features don't need to be disabled. AFAICT, this is a non-issue: no 64 bit seek means no large files.We are going to need to either get fseeko workarounds for those, or disable those features in a meaningful way.
I'm not sure we should even worry about it, but if you are genuinely concerned that we have no 64 bit seek call, but we do have files > 4GB, then If you really want to disable seek, just modify the code that sets 'hasSeek' - don't screw around with every seek call. But only modify clear it if the file is > 4GB.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
