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

Re: [GENERAL] WAL logs multiplexing?

From: Dmitry Panov <dmitry(at)tsu(dot)tula(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] WAL logs multiplexing?
Date: 2005-12-29 07:47:54
Message-ID: 1135842474.4246.9.camel@ip6-localhost (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
On Wed, 2005-12-28 at 11:05 -0500, Tom Lane wrote:
> Dmitry Panov <dmitry(at)tsu(dot)tula(dot)ru> writes:
> > Yes, but if the server has crashed earlier the script won't be called
> > and if the filesystem can't be recovered the changes will be lost. My
> > point is the server should write into both (or more) files at the same
> > time.
> 
> As for that, I agree with the other person: a RAID array does that just
> fine, and with much higher performance than we could muster.
> 

BTW, I found something related in the TODO:
http://momjian.postgresql.org/cgi-bin/pgtodo?pitr

I think both approaches have the right to exist, but I prefer my because
it looks more straightforward, it insures up-to-date recovery (no
delays) and it reduces the traffic (as the partial logs have to be
transferred in full by the proposed "archive_current_wal_command"). The
only drawback is performance.

Best regards,
-- 
Dmitry O Panov          | mailto:dmitry(at)tsu(dot)tula(dot)ru
Tula State University   | Fidonet: Dmitry Panov, 2:5022/5.13
Dept. of CS & NIT       | http://www.tsu.tula.ru/



In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2005-12-29 09:33:13
Subject: Re: localization problem (and solution)
Previous:From: Christopher Kings-LynneDate: 2005-12-29 07:14:03
Subject: Re: [COMMITTERS] pgsql: Minor doc tweak: "NOT NULL" is

pgsql-general by date

Next:From: Michael FuhrDate: 2005-12-29 07:56:52
Subject: Re: Validating User
Previous:From: Gregory S. WilliamsonDate: 2005-12-29 07:42:19
Subject: Re: Detaching database

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