From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Duplicate primary keys/rows |
Date: | 2005-10-10 21:28:17 |
Message-ID: | 5980.1128979697@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> On Mon, Oct 10, 2005 at 04:28:57PM -0400, Tom Lane wrote:
>> It's really highly annoying that we can't see the contents of the
>> infomasks for the rows.
> Any particular reason there isn't an infomask system column?
(a) inertia
(b) lack of desire to add an additional pg_attribute row per table.
I recall having proposed that we stop storing explicit pg_attribute
entries for system columns, which would make this sort of change easier
to make, and would save a pretty considerable amount of space in
pg_attribute too. (In the present regression database, about 45% of the
rows in pg_attribute are for system columns; that might be overly high
for real-world DBs though.) But people were a bit worried about what
might break.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-10-10 21:31:38 | Re: weird problem with grants |
Previous Message | Scott Marlowe | 2005-10-10 21:06:04 | Re: Duplicate primary keys/rows |