Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: wal sync method
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: PFC <lists(at)peufeu(dot)com>
- Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Javier Somoza" <jsomoza(at)pandasoftware(dot)es>, "Evgeny Gridasov" <eugrid(at)fpm(dot)kubsu(dot)ru>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: wal sync method
- Date: Tue, 28 Feb 2006 18:45:06 -0500
PFC <lists(at)peufeu(dot)com> writes: > Just a stupid question about the various fsync settings. > There is fsync=off, but is there fsync=fflush ? > fflush would mean only an OS crash could cause data loss, > I think.it could be useful for some applications where you need a speed > boost (like testing database import scripts...) without being as scary as > fsync=off... I think you misunderstand. There aren't any scenarios where a PG crash (without hardware/OS crash) risks data, because we always at least write() data before commit. The only issue is how hard do we try to get the OS+hardware to push that data down to disk. regards, tom lane
- References:
- Re: wal sync method
- From: Bruce Momjian
- Re: wal sync method
- From: PFC
- Re: wal sync method
- Prev by Date: Re: wal sync method
- Next by Date: [no subject]
- Previous by thread: Re: wal sync method
- Next by thread: Setting the shared buffers
- Indexes: