[EMAIL PROTECTED] (Leonardo Francalanci) writes:
>> 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 rea
Leonardo Francalanci <[EMAIL PROTECTED]> writes:
> Is there any documentation I can read about this?
The best concise documentation I know about is in the CVS-tip docs for
contrib/oid2name (reproduced below; the bit about tablespaces is
irrelevant to pre-8.0 versions, but the rest is accurate). I
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 ind
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)---
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.
The file name, that number, is the OID of the table afaik. And the
postfix is of course the number in the o
I got a table with oid 25459.
The file is 1073741824 bytes big.
I did some more inserts, and now I have this two new files:
size/name:
1073741824 25459.1
21053440 25459.2
What are they?
The 25459.1 looks exactly like the 25459.
I tried looking at the docs, but searching for ".1" or ".2" wasn't that
