| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | "Saleh, Amgad H (Amgad)" <ahsaleh(at)lucent(dot)com> |
| Cc: | Seum-Lim Gan <slgan(at)lucent(dot)com>, "'srn(at)commsecure(dot)com(dot)au'" <srn(at)commsecure(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Disk Usage and Page Size |
| Date: | 2004-03-18 17:57:50 |
| Message-ID: | 20040318095213.C51797@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 18 Mar 2004, Saleh, Amgad H (Amgad) wrote:
>
> Stephan:
>
> In each table we're storing the max. string length.
>
> For example:
>
> for TEST_1, we're storing 'abcdefghjk' and 'lmnop'
> for TEST_2, we're storing 'abcdefghjk' and 'lmnopqrstu'
> for TEST_3, we're storing 'abcdefghjk' and 'lmnopqrstuvw'
Hmm, on my machine it seemed like I was getting slightly different row
count per page results for the first two cases. The last two aren't going
to be different due to padding if the machine pads to 4 byte boundaries.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-03-18 18:23:14 | Re: fsync method checking |
| Previous Message | Bruce Momjian | 2004-03-18 17:46:13 | Re: [HACKERS] fsync method checking |