Re: Extremely Slow Cascade Delete Operation
От | Yan Cheng Cheok |
---|---|
Тема | Re: Extremely Slow Cascade Delete Operation |
Дата | |
Msg-id | 422045.90987.qm@web65707.mail.ac4.yahoo.com обсуждение исходный текст |
Ответ на | Re: Extremely Slow Cascade Delete Operation (Craig Ringer <craig@postnewspapers.com.au>) |
Список | pgsql-general |
OMG, I never know what is index (Sorry for my newbies) I will study about them and update you all about their performance. Thanks and Regards Yan Cheng CHEOK --- On Wed, 1/13/10, Craig Ringer <craig@postnewspapers.com.au> wrote: > From: Craig Ringer <craig@postnewspapers.com.au> > Subject: Re: [GENERAL] Extremely Slow Cascade Delete Operation > To: "Yan Cheng Cheok" <yccheok@yahoo.com> > Cc: pgsql-general@postgresql.org > Date: Wednesday, January 13, 2010, 7:01 PM > On 13/01/2010 4:09 PM, Yan Cheng > Cheok wrote: > > I have 3 tables - lot, unit and measurement > > > > 1 lot is having relationship to many unit. > > 1 unit is having relationship to many measurement. > > delete cascade is being used among their relationship > > > > > SemiconductorInspection=# delete from lot where lot_id > = 2; > > Are there indexes on fk_lot_id and fk_unit_id ? If not, a > DELETE from lot will cause a seqscan of unit for affected > units, and if any must be deleted each will cause a seqscan > of measurement for affected measurements. That's going to > get ugly fast. > > -- > Craig Ringer > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
В списке pgsql-general по дате отправления: