| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Alex Hunsaker" <badalex(at)gmail(dot)com> |
| Cc: | NikhilS <nikkhils(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Pg Patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [badalex@gmail.com: Re: [BUGS] Problem identifying constraints which should not be inherited] |
| Date: | 2008-05-07 13:52:18 |
| Message-ID: | 5873.1210168338@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
> Currently this loops through all the constraints for a relation (old
> behavior of MergeAttributesIntoExisting)... Do you think its worth
> adding a non-unique index to speed this up?
No. If we were to refactor pg_constraint as I mentioned earlier,
then it could have a natural primary key (reloid, constrname)
(replacing the existing nonunique index on reloid) and then a number
of things could be sped up. But just piling more indexes on a
fundamentally bad design doesn't appeal to me ...
Will review the revised patch today.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-05-07 13:56:48 | Behaviour of MERGE with complex Rules |
| Previous Message | Andrew Sullivan | 2008-05-07 13:37:49 | Re: [0/4] Proposal of SE-PostgreSQL patches |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-05-07 14:00:03 | Re: [PATCHES] Testing pg_terminate_backend() |
| Previous Message | Andrew Sullivan | 2008-05-07 13:37:49 | Re: [0/4] Proposal of SE-PostgreSQL patches |