| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: fillfactor using WITH syntax |
| Date: | 2006-06-06 14:27:53 |
| Message-ID: | 16981.1149604073@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> Why not implement an array of option parameters on pg_class, so both
> heaps and indexes can be given additional parameters? That way you
> wouldn't need a specific relfillfactor attribute. That would allow us to
> keep CREATE TABLE free of additional keywords also.
None of this should go anywhere near pg_class. IIRC the solutions we
discussed involved adding some sort of array to pg_index. A solution
that only works for FILLFACTOR is missing the point, too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-06-06 14:39:19 | Re: [PERFORM] psql -A (unaligned format) eats too much |
| Previous Message | Tom Lane | 2006-06-06 14:19:42 | Re: Duplicate rows sneaking in despite PRIMARY KEY / UNIQUE constraint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-06 14:31:30 | Re: 'Index Full Scan' for Index Scan without Index Cond |
| Previous Message | Simon Riggs | 2006-06-06 14:22:46 | Why do we have a WAL record for CLOG page extension? |