Re: PG on NFS may be just a bad idea

Поиск
Список
Период
Сортировка
Искать
От
Neil Conway
Тема
Re: PG on NFS may be just a bad idea
Дата
Msg-id
1191878537.26227.4.camel@dell.linuxdev.us.dell.com
Ответ на
Список
Дерево обсуждения
PG on NFS may be just a bad idea Tom Lane <tgl@sss.pgh.pa.us>
Re: PG on NFS may be just a bad idea Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Re: PG on NFS may be just a bad idea Josh Berkus <josh@agliodbs.com>
Re: PG on NFS may be just a bad idea Simon Riggs <simon@2ndquadrant.com>
Re: PG on NFS may be just a bad idea Simon Riggs <simon@2ndquadrant.com>
Re: PG on NFS may be just a bad idea Tom Lane <tgl@sss.pgh.pa.us>
Re: PG on NFS may be just a bad idea Simon Riggs <simon@2ndquadrant.com>
Re: PG on NFS may be just a bad idea Alvaro Herrera <alvherre@commandprompt.com>
Re: PG on NFS may be just a bad idea Bruce Momjian <bruce@momjian.us>
Re: PG on NFS may be just a bad idea Alvaro Herrera <alvherre@commandprompt.com>
Re: PG on NFS may be just a bad idea Neil Conway <neilc@samurai.com>
Re: PG on NFS may be just a bad idea Tom Lane <tgl@sss.pgh.pa.us>
On Mon, 2007-10-08 at 16:50 -0400, Alvaro Herrera wrote:
> palloc uses malloc underneath.  My thought is to replace that with
> sbrk, mmap or something like that.  Not very portable though, a lot of
> work, and most likely not nearly enough benefits.

Yeah, I agree this isn't likely to be a win in the general case.
However, it would be interesting to explore a specialized allocator for
short-lived memory contexts, where we don't care about having an
effective pfree(). If the context is going to be reset or deleted
shortly anyway, we could probably optimize and simplify palloc() by
skipping free space accounting and then make pfree() a no-op. I recall
Tom mentioning something to this effect a few months back...

-Neil



В списке pgsql-hackers по дате отправления
От: Gregory Stark
Дата:
От: Robert Treat
Дата:
FAQ