----- Original Message ---- >From: Jim C. Nasby <jnasby@xxxxxxxxxxxxx> >To: Shelby Cain <alyandon@xxxxxxxxx> >Cc: Csaba Nagy <nagy@xxxxxxxxxxxxxx>; SCassidy@xxxxxxxxxxxxxxxxxxx; Postgres >general mailing list <pgsql-general@xxxxxxxxxxxxxx>; pgsql-general-owner@xxxxxxxxxxxxxx >Sent: Tuesday, May 23, 2006 5:19:58 PM >Subject: Re: [GENERAL] allow LIMIT in UPDATE and DELETE > >The issue is that vacuum has to base it's decisions not on the oldest >running transaction that has locks on a table, but on the oldest running >transaction in the entire database, because that transaction could start >reading any table at any time. Until that changes, long-running >transactions of any kind and heavy-update tables simply won't mix well >at all in a single database. Now I understand... thanks for the clarification. Regards, Shelby Cain
