Re: [PATCHES] GIN improvements
От | Jeff Davis |
---|---|
Тема | Re: [PATCHES] GIN improvements |
Дата | |
Msg-id | 1232474489.23316.8.camel@jdavis обсуждение исходный текст |
Ответ на | Re: [PATCHES] GIN improvements (Teodor Sigaev <teodor@sigaev.ru>) |
Ответы |
New pg_dump patch, --no-stats flag, disables sending to statistics
collector
Re: [PATCHES] GIN improvements |
Список | pgsql-hackers |
On Mon, 2009-01-19 at 19:53 +0300, Teodor Sigaev wrote: > I see only two guaranteed solution of the problem: > - after limit is reached, force normal index inserts. One of the motivation of > patch was frequent question from users: why update of whole table with GIN index > is so slow? So this way will not resolve this question. > - after limit is reached, force cleanup of pending list by calling > gininsertcleanup. Not very good, because users sometimes will see a huge > execution time of simple insert. Although users who runs a huge update should be > satisfied. > > I have difficulties in a choice of way. Seems to me, the better will be second > way: if user gets very long time of insertion then (auto)vacuum of his > installation should tweaked. > I agree that the second solution sounds better to me. With the new Visibility Map, it's more reasonable to run VACUUM more often, so those that are inserting single tuples at a time should not encounter the long insert time. I'm still looking at the rest of the patch. Regards,Jeff Davis
В списке pgsql-hackers по дате отправления: