Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] SRA Win32 sync() code

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>,PostgreSQL Win32 port list <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [PATCHES] SRA Win32 sync() code
Date: 2003-11-16 16:36:54
Message-ID: 200311161636.hAGGatT23547@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32pgsql-patches
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Not sure how we are going to do this in Win32, but somehow we will have
> > to record all open files between checkpoints in an area that the
> > checkpoint process can read during a checkpoint.
> 
> One reason I like the idea of adopting a sync-when-you-write policy is
> that it eliminates the need for anything as messy as that.

Yes, but can we do it without causing a performance degredation, and I
would hate to change something to make things easier on Win32 while
penalizing all platforms.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

Responses

pgsql-hackers by date

Next:From: Jan WieckDate: 2003-11-16 16:46:01
Subject: Re: cvs head? initdb?
Previous:From: Tom LaneDate: 2003-11-16 16:32:59
Subject: Re: [PATCHES] SRA Win32 sync() code

pgsql-patches by date

Next:From: Tom LaneDate: 2003-11-16 16:58:12
Subject: Re: [PATCHES] SRA Win32 sync() code
Previous:From: Tom LaneDate: 2003-11-16 16:32:59
Subject: Re: [PATCHES] SRA Win32 sync() code

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2003-11-16 16:58:12
Subject: Re: [PATCHES] SRA Win32 sync() code
Previous:From: Tom LaneDate: 2003-11-16 16:32:59
Subject: Re: [PATCHES] SRA Win32 sync() code

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group