Re: Breakage with VACUUM ANALYSE + partitions
От | Robert Haas |
---|---|
Тема | Re: Breakage with VACUUM ANALYSE + partitions |
Дата | |
Msg-id | CA+TgmoZiF3_hG8-M6hq_Z-O=VoyNd9FtbmVTw+YcM+Fn-m_rfw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Breakage with VACUUM ANALYSE + partitions (Haribabu Kommi <kommi.haribabu@gmail.com>) |
Ответы |
Re: Breakage with VACUUM ANALYSE + partitions
|
Список | pgsql-bugs |
On Thu, Mar 24, 2016 at 12:59 AM, Haribabu Kommi <kommi.haribabu@gmail.com> wrote: > So further operations on the table uses the already constructed smgr relation > and treats that there are RELSEG_SIZE number of blocks in the page and try > to do the scan. But there are 0 pages in the table thus it produces the error. > > The issue doesn't occur from another session. Because of this reason only > if we do only vacuum operation, the error not occurred. Yeah, I had a suspicion that this might have to do with invalidation messages based on Thom's description, but I think we still need to track down which commit is at fault. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-bugs по дате отправления: