Hideyuki Kawashima wrote:
> 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.
The question then is how much faster is it, and is that worth adding
extra code to improve it.
---------------------------------------------------------------------------
>
> -- 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.
> >
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
