pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Stone <mstone+postgres@mathom.us>
To: pgsql-performance@postgresql.org
Subject: Re: extremly low memory usage
Date: Sat, 20 Aug 2005 08:23:05 -0400
Message-ID: <20050820122305.GN19080@mathom.us> (raw)
In-Reply-To: <43071162.6050405@kolumbus.fi>
References: <EA4219B9-E2B0-4756-ABF2-D84F245FDFB5@torgo.978.org>
	<1124386761.27881.119.camel@bluejay.goodinassociates.com>
	<4304CB77.4070403@arbash-meinel.com>
	<1124470109.27881.152.camel@bluejay.goodinassociates.com>
	<43061472.2080201@arbash-meinel.com>
	<6.2.3.4.0.20050819140714.05c181e8@pop.earthlink.net>
	<43063196.9000001@arbash-meinel.com>
	<1124485299.27881.192.camel@bluejay.goodinassociates.com>
	<EFA54B85-504E-453A-972D-A7DD0E144763@drivefaster.net>
	<43071162.6050405@kolumbus.fi>

On Sat, Aug 20, 2005 at 02:17:54PM +0300, Marko Ristola wrote:
>Based on my knoledge, Ext3 is good with keeping filesystem integrity
>AND data integrity while pressing the reset button.  However, by
>selecting data=writeback, you gain more speed, but you risk the data
>integrity during a crash: Ext3 garantees only filesystem integrity.

That's why postgres keeps its own transaction log. Any of these
filesystems guarantee data integrity for data that's been synced to
disk, and postgres keeps track of what data has and has not been
committed so it can recover gracefully from a failure. That's why most
filesystems are designed the way they are; the application can determine
what things need better data integrity and which need better performance
on a case-by-case basis. 

Mike Stone



view thread (39+ messages)  latest in thread

Message-ID: <20050820122305.GN19080@mathom.us>
Permalink:  ../20050820122305.GN19080@mathom.us/
Also on:    postgresql.org/message-id/20050820122305.GN19080@mathom.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mstone+postgres@mathom.us
  Subject: Re: extremly low memory usage
  In-Reply-To: <20050820122305.GN19080@mathom.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox