| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
| Date: | 2009-04-05 02:56:02 |
| Message-ID: | 9591.1238900162@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> FWIW it has been said that whoever is concerned about pg_attribute bloat
> should be first looking at getting rid of the redundant entries for
> system columns, for each and every table.
That's been overtaken by events, unfortunately: we now need those
entries to carry per-column permissions on system columns. So they're
no longer merely overhead.
Possibly we could hack things so that only system columns with
non-default permissions are actually stored, but that feels like
a kluge.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-04-05 02:56:21 | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
| Previous Message | Robert Haas | 2009-04-05 02:39:34 | Re: a few crazy ideas about hash joins |