| From: | Arjen van der Meijden <acmmailing(at)vulcanus(dot)its(dot)tudelft(dot)nl> |
|---|---|
| To: | Leonardo Francalanci <lfrancalanci(at)simtel(dot)ie> |
| Cc: | postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: files ending with .1 or .2 |
| Date: | 2004-10-20 08:50:21 |
| Message-ID: | 417626CD.5050005@vulcanus.its.tudelft.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I don't know. I just deduced that from an earlier situation where I new
the size of the data, and noticed that the largest table was split up in
enough 1GB parts to fit that size ;)
Best regards,
Arjen
On 20-10-2004 10:14, Leonardo Francalanci wrote:
>> When a data file for a specific table (or index?) is larger than 1GB,
>> its split up in several parts. This is probably a left over from the
>> time OSs used to have problems with large files.
>
>
> Thank you.
> Is there any documentation I can read about this?
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-10-20 08:51:47 | Re: beta3 winxp initdb problems |
| Previous Message | Leonardo Francalanci | 2004-10-20 08:14:06 | Re: files ending with .1 or .2 |