From: | "Lawrence Cohan" <lawrencec(at)1shoppingcart(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #4238: pg_class.relhasindex not updated by vacuum |
Date: | 2008-06-13 17:03:27 |
Message-ID: | D125F8AF679AEE4390F3A546AFFA5CB00331A3DC@hermes.1shoppingcart.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Many thanks again. I figured out how to get only the tables that have
indexes created less these PK indexes so I can used the pg_get_indexdef
to rebuild them all through a scheduled Pgagent job in a loop using
CONCURRENTLY as our production assumes DB access 24/7.
Lawrence Cohan.
-----Original Message-----
From: Alvaro Herrera [mailto:alvherre(at)commandprompt(dot)com]
Sent: Friday, June 13, 2008 12:57 PM
To: Lawrence Cohan
Cc: Tom Lane; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #4238: pg_class.relhasindex not updated by
vacuum
Lawrence Cohan wrote:
> Isn't a PK a CONSTRAINT and not an INDEX???
Sure, from a logical point of view. The implementation of that
constraint is an index.
> 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.
What would be the point? If you want to figure out whether a table has
a primary key, you can query the catalogs.
--
Alvaro Herrera
http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-06-13 17:12:41 | Re: BUG #4238: pg_class.relhasindex not updated by vacuum |
Previous Message | Alvaro Herrera | 2008-06-13 16:56:45 | Re: BUG #4238: pg_class.relhasindex not updated by vacuum |