pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Reiser4
5+ messages / 4 participants
[nested] [flat]

* Reiser4
@ 2004-08-13 16:12 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
  2004-08-13 18:01 ` Re: Reiser4 Josh Berkus <josh@agliodbs.com>
  2004-08-14 01:30 ` Re: [PERFORM] Reiser4 Bruce Momjian <pgman@candle.pha.pa.us>
  0 siblings, 2 replies; 5+ messages in thread

From: Pierre-Frédéric Caillaud @ 2004-08-13 16:12 UTC (permalink / raw)
  To: pgsql-performance



	ReiserFS 4 is (will be) a filesystem that implements transactions.

	Are there any plans in a future Postgresql version to support a special  
fsync method for Reiser4 which will use the filesystem's transaction  
engine, instead of an old kludge like fsync(), with a possibility of  
vastly enhanced performance ?

	Is there also a possibility to tell Postgres : "I don't care if I lose 30  
seconds of transactions on this table if the power goes out, I just want  
to be sure it's still ACID et al. compliant but you can fsync less often  
and thus be faster" (with a possibility of setting that on a per-table  
basis) ?

	Thanks.



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Reiser4
  2004-08-13 16:12 Reiser4 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
@ 2004-08-13 18:01 ` Josh Berkus <josh@agliodbs.com>
  2004-08-14 01:31   ` Re: Reiser4 Bruce Momjian <pgman@candle.pha.pa.us>
  1 sibling, 1 reply; 5+ messages in thread

From: Josh Berkus @ 2004-08-13 18:01 UTC (permalink / raw)
  To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>; pgsql-performance

Pierre,

> 	Are there any plans in a future Postgresql version to support a special  
> fsync method for Reiser4 which will use the filesystem's transaction  
> engine, instead of an old kludge like fsync(), with a possibility of  
> vastly enhanced performance ?

I don't know of any such in progress right now.  Why don't you start it?  It 
would have to be an add-in since we support 28 operating systems and Reiser 
is AFAIK Linux-only, but it sounds like an interesting experiment.

> 	Is there also a possibility to tell Postgres : "I don't care if I lose 30  
> seconds of transactions on this table if the power goes out, I just want  
> to be sure it's still ACID et al. compliant but you can fsync less often  
> and thus be faster" (with a possibility of setting that on a per-table  
> basis) ?

Not per-table, no, but otherwise take a look at the Background Writer feature 
of 8.0.

-- 
-Josh Berkus
 "A developer of Very Little Brain"
 Aglio Database Solutions
 San Francisco




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Reiser4
  2004-08-13 16:12 Reiser4 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
  2004-08-13 18:01 ` Re: Reiser4 Josh Berkus <josh@agliodbs.com>
@ 2004-08-14 01:31   ` Bruce Momjian <pgman@candle.pha.pa.us>
  0 siblings, 0 replies; 5+ messages in thread

From: Bruce Momjian @ 2004-08-14 01:31 UTC (permalink / raw)
  To: josh@agliodbs.com; +Cc: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>; pgsql-performance

Josh Berkus wrote:
> Pierre,
> 
> > 	Are there any plans in a future Postgresql version to support a special  
> > fsync method for Reiser4 which will use the filesystem's transaction  
> > engine, instead of an old kludge like fsync(), with a possibility of  
> > vastly enhanced performance ?
> 
> I don't know of any such in progress right now.  Why don't you start it?  It 
> would have to be an add-in since we support 28 operating systems and Reiser 
> is AFAIK Linux-only, but it sounds like an interesting experiment.
> 
> > 	Is there also a possibility to tell Postgres : "I don't care if I lose 30  
> > seconds of transactions on this table if the power goes out, I just want  
> > to be sure it's still ACID et al. compliant but you can fsync less often  
> > and thus be faster" (with a possibility of setting that on a per-table  
> > basis) ?
> 
> Not per-table, no, but otherwise take a look at the Background Writer feature 
> of 8.0.

Actually the fsync of WAL is the big performance issue here.  I added a
TODO item about it.

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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: [PERFORM] Reiser4
  2004-08-13 16:12 Reiser4 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
@ 2004-08-14 01:30 ` Bruce Momjian <pgman@candle.pha.pa.us>
  2004-08-14 10:57   ` Re: [PERFORM] Reiser4 Peter Eisentraut <peter_e@gmx.net>
  1 sibling, 1 reply; 5+ messages in thread

From: Bruce Momjian @ 2004-08-14 01:30 UTC (permalink / raw)
  To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>; +Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>

Pierre-Frédéric Caillaud wrote:
> 	Is there also a possibility to tell Postgres : "I don't care if I lose 30  
> seconds of transactions on this table if the power goes out, I just want  
> to be sure it's still ACID et al. compliant but you can fsync less often  
> and thus be faster" (with a possibility of setting that on a per-table  
> basis) ?

I have been thinking about this.  Informix calls it buffered logging and
it would be a good feature.

Added to TODO:

* Allow buffered WAL writes and fsync

  Instead of guaranteeing recovery of all committed transactions, this
  would provide improved performance by delaying WAL writes and fsync
  so an abrupt operating system restart might lose a few seconds of
  committed transactions but still be consistent.  We could perhaps
  remove the 'fsync' parameter (which results in an an inconsistent
  database) in favor of this capability.

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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: [PERFORM] Reiser4
  2004-08-13 16:12 Reiser4 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
  2004-08-14 01:30 ` Re: [PERFORM] Reiser4 Bruce Momjian <pgman@candle.pha.pa.us>
@ 2004-08-14 10:57   ` Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 0 replies; 5+ messages in thread

From: Peter Eisentraut @ 2004-08-14 10:57 UTC (permalink / raw)
  To: Bruce Momjian <pgman@candle.pha.pa.us>; Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>; +Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>

Bruce Momjian wrote:
> Pierre-Frédéric Caillaud wrote:
> > 	Is there also a possibility to tell Postgres : "I don't care if I
> > lose 30 seconds of transactions on this table if the power goes
> > out, I just want to be sure it's still ACID et al. compliant but
> > you can fsync less often and thus be faster" (with a possibility of
> > setting that on a per-table basis) ?

Then it would be "ACI" compliant.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/




^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2004-08-14 10:57 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-08-13 16:12 Reiser4 Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
2004-08-13 18:01 ` Josh Berkus <josh@agliodbs.com>
2004-08-14 01:31   ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-08-14 01:30 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-08-14 10:57   ` Peter Eisentraut <peter_e@gmx.net>

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