| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Karim Nassar <karim(dot)nassar(at)NAU(dot)EDU>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Delete query takes exorbitant amount of time |
| Date: | 2005-03-26 06:31:58 |
| Message-ID: | 424501DE.5010603@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> There is clear benefit from forcing them to be the same. In logical data
> terms, they *should* be the same. I don't check fruit.apple_grade
> against fruit_type.orange_grade. When would I want to make a check of
> that nature? If there is a reason, thats great, lets keep status quo
> then.
>
> I respect the effort and thought that has already gone into the
> implementation; I seek only to offer a very minor improvement based upon
> recent list issues.
The main problem would be people getting errors when upgrading their
databases, or restoring from a backup, say.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bjoern Metzdorf | 2005-03-26 09:59:15 | Re: How to improve db performance with $7K? |
| Previous Message | Alexander Kirpa | 2005-03-26 03:21:25 | Re: How to improve db performance with $7K? |