| From: | Mario Weilguni <mweilguni(at)sime(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | number of attributes in page files? |
| Date: | 2002-10-11 07:14:50 |
| Message-ID: | 200210110914.50377.mweilguni@sime.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Is it possible to get rid of the "t_natts" fields in the tuple header? Is this field only for "alter table add/drop" support? Then it might
possible to get rid of it and put the "t_natts" field in the page header, not the tuple header, if it can be assured that when updating/inserting
records only a compatible (a page file with the same number of attributes) page file is used. Especially master-detail tables would
profit from this, reducing the tuple overhead by another 9%.
Might this be possible?
Regards,
Mario Weilguni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Jürgen Schönig | 2002-10-11 07:21:29 | Suggestion: Helping the optimizer |
| Previous Message | Bruce Momjian | 2002-10-11 05:17:02 | Re: [Fwd: Re: [JDBC] Patch for handling "autocommit=false" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario Weilguni | 2002-10-11 08:44:03 | Compile test with gcc 3.2 |
| Previous Message | Josh Berkus | 2002-10-10 16:59:18 | Re: Info on explain output |