From: | "Lawrence Cohan" <lawrencec(at)1shoppingcart(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #4238: pg_class.relhasindex not updated by vacuum |
Date: | 2008-06-13 16:45:10 |
Message-ID: | D125F8AF679AEE4390F3A546AFFA5CB00331A3DB@hermes.1shoppingcart.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Isn't a PK a CONSTRAINT and not an INDEX???
Some say "one or more fields" and others "one or more attributes" that
uniquely identifies a record in a table and PG like many other databases
would create a default internal index on that CONSTRAINT that can't be
seen or dropped unless you will drop the Pkey.
In that case the two separate pg_class relhasindex and relhaspkey would
make sense indeed - just a thought nothing else and we'll take it as is.
Best regards,
Lawrence Cohan.
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, June 13, 2008 12:33 PM
To: Lawrence Cohan
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #4238: pg_class.relhasindex not updated by
vacuum
"Lawrence Cohan" <lawrencec(at)1shoppingcart(dot)com> writes:
> Is it possible that because of the PKEY's we have on the tables that
> flag is still showing "true"?
Uh, well certainly -- a PK is an index.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-06-13 16:56:45 | Re: BUG #4238: pg_class.relhasindex not updated by vacuum |
Previous Message | Tom Lane | 2008-06-13 16:32:38 | Re: BUG #4238: pg_class.relhasindex not updated by vacuum |