Re: Acclerating INSERT/UPDATE using UPS
От | Hideyuki Kawashima |
---|---|
Тема | Re: Acclerating INSERT/UPDATE using UPS |
Дата | |
Msg-id | 45D1109B.1070304@cs.tsukuba.ac.jp обсуждение исходный текст |
Ответ на | Re: Acclerating INSERT/UPDATE using UPS (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: Acclerating INSERT/UPDATE using UPS
|
Список | pgsql-hackers |
Bruce, Thanks for your comments, and let me answer to your question. Sigres is *not* significantly faster than just creating a file system on the permanent memory and putting xlog on there. Sigres is slightly faster than the case because each backend does not call XLogWrite while bgWriter does. -- Hideyuki Bruce Momjian wrote: > Tom Lane wrote: > >> Gene <genekhart@gmail.com> writes: >> >>> ... just my two cents. on a side note, would putting the wal on a >>> tmpfs partition give you something similar? >>> >> Indeed, I'm wondering why one needs to hack the Postgres core to throw >> away data integrity guarantees; there are plenty of ways to do that >> already :-(. Hideyuki-san has not explained exactly what integrity >> assumptions he wants to make or not make. I'm surely willing to listen >> to supporting a different set of assumptions than we currently use, but >> I'd like to see a clear explanation of what assumptions are being made >> and why they represent a useful case. >> > > I am unsure why Sigres is significantly faster than just creating a file > system on the permanent memory and putting xlog on there. > >
В списке pgsql-hackers по дате отправления: