From: Tom Lane
Subject: Re: PG8 Tuning
Date: ,
Msg-id: 10092.1124245640@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: PG8 Tuning  (John A Meinel)
List: pgsql-performance

Tree view

PG8 Tuning  ("Paul Johnson", )
 Re: PG8 Tuning  (Richard Huxton, )
 [SPAM?] Re: PG8 Tuning  (Steve Poe, )
  Re: [SPAM?] Re: PG8 Tuning  ("Jeffrey W. Baker", )
   Re: [SPAM?] Re: PG8 Tuning  (Jeff Trout, )
   Re: [SPAM?] Re: PG8 Tuning  (Josh Berkus, )
    Re: [SPAM?] Re: PG8 Tuning  (Alvaro Herrera <-ip.org>, )
     Re: [SPAM?] Re: PG8 Tuning  ("Joshua D. Drake", )
     Re: PG8 Tuning  (John A Meinel, )
      Re: PG8 Tuning  (Tom Lane, )
       Re: PG8 Tuning  (John A Meinel, )
        Re: PG8 Tuning  (Tom Lane, )
    Re: [SPAM?] Re: PG8 Tuning  (Michael Stone, )
     Re: PG8 Tuning  (Josh Berkus, )
  Re: [SPAM?] Re: PG8 Tuning  (Tom Arthurs, )
  Re: PG8 Tuning  (Mark Lewis, )
   Re: PG8 Tuning  (Michael Stone, )
 Re: PG8 Tuning  (Michael Stone, )
 Re: PG8 Tuning  ("Merlin Moncure", )

John A Meinel <> writes:
> So pg_xlog is really only needed for a dirty shutdown. So what about the
> idea of having pg_xlog on a ramdisk that is syncronized periodically to
> a real disk.

Well, if "periodically" means "at every transaction commit", that's
pretty much what we do now.

            regards, tom lane


pgsql-performance by date:

From: mudfoot@rawbw.com
Date:
Subject: Re: Performance problem using V3 protocol in jdbc driver
From: Ulrich Wisser
Date:
Subject: Re: Need for speed