From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | "G(dot) Anthony Reina" <reina(at)nsi(dot)edu> |
Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Extending to 32K row limit |
Date: | 2000-08-08 17:51:16 |
Message-ID: | 3.0.1.32.20000808105116.01446e00@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 11:17 AM 8/8/00 -0700, G. Anthony Reina wrote:
>Thanks Don. One more question: Does Postgres set aside an entire 8 K (or
32 K) of
>hard disk space for the row; or, does it just use what's needed to store the
>information? For example, if I only have one integer value in a row, does
Postgres
>set aside 8K of harddrive space or just sizeof(int) space (with some
pointer where
>other values in the row could be placed on the disk)?
No, it does not allocate a fixed 8K (or 32K) block per row. The size of a
row is dependent on the data stored within the row. Each row also contains
a header of modest length.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Darren King | 2000-08-08 18:14:50 | RE: Extending to 32K row limit |
Previous Message | Don Baccus | 2000-08-08 17:34:04 | Re: Extending to 32K row limit |