From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tilo Schwarz <mail(at)tilo-schwarz(dot)de> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Vacuum explained |
Date: | 2003-01-08 04:02:41 |
Message-ID: | 597.1041998561@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tilo Schwarz <mail(at)tilo-schwarz(dot)de> writes:
> Do you try to reuse tuples with a similar storage size (or something like
> that)
No. If we try to put a tuple on a page, and there's room there, we'll
store it. There is no intra-page fragmentation problem because we can
always reshuffle the tuples on a particular page --- this is what the
"page item pointer" overhead buys us.
Also, since any given file only holds tuples of a particular table,
there's already some degree of size-similarity present. This gets
pretty weak if some of the fields are of widely varying length, of
course, but I'm dubious that there's much gold to be mined by thinking
harder about which page we put a tuple on...
> Any pointers to documentation or into the source code are welcome!
The comments at the head of src/include/storage/bufpage.h might be
illuminating. Also see
http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/page.html
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-08 04:12:31 | Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm |
Previous Message | D'Arcy J.M. Cain | 2003-01-08 02:51:48 | Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm |