Re: still gin index creation takes forever

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: still gin index creation takes forever
Дата
Msg-id
19874.1226521085@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Postgres 8.2.x support on Windows 2008 "Raji Sridar (raji)" <raji@cisco.com>
Re: Postgres 8.2.x support on Windows 2008 Raymond O'Donnell <rod@iol.ie>
Re: Postgres 8.2.x support on Windows 2008 "Joshua D. Drake" <jd@commandprompt.com>
Re: Postgres 8.2.x support on Windows 2008 Scott Marlowe <scott.marlowe@gmail.com>
[Q] ODBC connect shows RELEASE / SAVEPOINT on selects "V S P" <toreason@fastmail.fm>
[Q] ODBC Decimal(19,6) "V S P" <toreason@fastmail.fm>
Re: Postgres 8.2.x support on Windows 2008 "Raji Sridar (raji)" <raji@cisco.com>
Re: Postgres 8.2.x support on Windows 2008 "Joshua D. Drake" <jd@commandprompt.com>
Re: Postgres 8.2.x support on Windows 2008 "Raji Sridar (raji)" <raji@cisco.com>
Re: Postgres 8.2.x support on Windows 2008 Magnus Hagander <magnus@hagander.net>
Re: Postgres 8.2.x support on Windows 2008 Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres 8.2.x support on Windows 2008 "Joshua D. Drake" <jd@commandprompt.com>
Re: Postgres 8.2.x support on Windows 2008 Craig Ringer <craig@postnewspapers.com.au>
Re: Postgres 8.2.x support on Windows 2008 Dave Page <dpage@pgadmin.org>
Re: Postgres 8.2.x support on Windows 2008 Magnus Hagander <magnus@hagander.net>
Re: Postgres 8.2.x support on Windows 2008 "Dann Corbit" <DCorbit@connx.com>
Re: Postgres 8.2.x support on Windows 2008 John R Pierce <pierce@hogranch.com>
Re: Postgres 8.2.x support on Windows 2008 Howard Cole <howardnews@selestial.com>
Re: Postgres 8.2.x support on Windows 2008 Scott Marlowe <scott.marlowe@gmail.com>
Teodor Sigaev  writes:
>> I'm not following.  Rightmost page of what --- it can't be the whole
>> index, can it, or the case would hardly ever apply?

> GIN's index contains btree over keys (entry tree) and for each key it 
> contains list of ItemPointers (posting list) or btree over ItemPointers 
> (posting tree or data tree) depending on its quantity. Bulk insertion 
> process collects into memory keys and sorted arrays of ItemPointers, and 
> then for each keys, it tries to insert every ItemPointer from array into 
> corresponding data tree one by one. But if the smallest ItemPointer in 
> array is greater than the biggest stored one then algorithm will insert 
> the whole array on rightmost page in data tree.

> So, in that case process can insert about 1000 ItemPointers per one data 
> tree lookup, in opposite case it does 1000 lookups in data tree.

I see.  So this could explain Ivan's issue if his table contains large
numbers of repeated GIN keys.  Ivan, is that what your data looks like?

			regards, tom lane
В списке pgsql-general по дате отправления
От: paulo matadr
Дата:
От: Robert Fitzpatrick
Дата:
FAQ