Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split
От | Alvaro Herrera |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split |
Дата | |
Msg-id | 20070208135916.GA24069@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split (Heikki Linnakangas <heikki@enterprisedb.com>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page
splits: > Currently, an index split
|
Список | pgsql-hackers |
Heikki Linnakangas wrote: > Stefan Kaltenbrunner wrote: > >Bruce Momjian wrote: > >>Log Message: > >>----------- > >>Reduce WAL activity for page splits: > >> > >>>Currently, an index split writes all the data on the split page to > >>>WAL. That's a lot of WAL traffic. The tuples that are copied to the > >>>right page need to be WAL logged, but the tuples that stay on the > >>>original page don't. > > > > > >this patch killed both of my OpenBSD buildfarm members Please note that zebra died for a different reason the second time (not enough shared memory). > lopaque was referenced after pfreeing the temp page it pointed to. Also > later in the function the LSN of the left page was set, but again using > a pointer to the pfreed temp copy instead of the real shared memory buffer. Applied, thanks. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: