Re: [Testperf-general] Re: ExclusiveLock
От | Simon Riggs |
---|---|
Тема | Re: [Testperf-general] Re: ExclusiveLock |
Дата | |
Msg-id | 1100817806.4113.10444.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: [Testperf-general] Re: ExclusiveLock (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [Testperf-general] Re: ExclusiveLock
Re: [Testperf-general] Re: ExclusiveLock |
Список | pgsql-hackers |
On Thu, 2004-11-18 at 22:12, Tom Lane wrote: > Josh Berkus <josh@agliodbs.com> writes: > > Aside from foriegn keys, though, is there any way in which INSERT page locks > > could block other inserts? > > Not for longer than the time needed to physically add a tuple to a page. The main problem on INSERTs is that it is usually the same few pages: the lead data block and the lead index block. There are ways of spreading the load out across an index, but I'm not sure what happens on the leading edge of the data relation, but I think it hits the same block each time. Only an issue if you have more than one CPU... -- Best Regards, Simon Riggs
В списке pgsql-hackers по дате отправления: