Re: heap vacuum & cleanup locks
От | Simon Riggs |
---|---|
Тема | Re: heap vacuum & cleanup locks |
Дата | |
Msg-id | CA+U5nMK4i__0VCEODof7PpDrxORXfYUiUkyMthiRgbJece87AA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: heap vacuum & cleanup locks (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: heap vacuum & cleanup locks
|
Список | pgsql-hackers |
On Wed, Nov 9, 2011 at 9:12 PM, Robert Haas <robertmhaas@gmail.com> wrote: > Well, I'm not sure of the details of how page-at-a-time mode works for > seq scans, but I am absolutely 100% sure that you can reproduce this > problem using a cursor over a sequential scan. Just do this: > > create table test (a text); > insert into test values ('aaa'), ('bbb'); > delete from test where a = 'aaa'; > begin; > declare x cursor for select * from test; > fetch next from x; That's a bug. heapam.c line 1202 says /* * we can use page-at-a-time mode if it's an MVCC-safe snapshot */scan->rs_pageatatime = IsMVCCSnapshot(snapshot); So either the comment or the code is wrong. Can't see where, as yet. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: