Date: Sat, 9 Aug 2008 16:01:40 +0200 From: Axel Rau <Axel.Rau@chaos1.de> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-database@freebsd.org Subject: Re: PostgreSQL 3.3 on gjournaled fs Message-ID: <3B2D25A1-5A0D-4163-A248-E709ADD54CC5@Chaos1.DE> In-Reply-To: <g7jmi6$dsa$1@ger.gmane.org> References: <8A4CC87D-8B69-4120-BB89-F794E4FFD871@Chaos1.DE> <g7jmi6$dsa$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 09.08.2008 um 11:03 schrieb Ivan Voras: > The question is - why do you need gjournal? PostgreSQL (and other > decent databases) does its own journaling (search for WAL), so using > it on a journaled file system doesn't do much. I want to prevent from fsck on large filesystems after outage. > > > If you really want it, it won't hurt you. Journal size needs to be > scaled based on your load. If you have constant writes you need a > larger journal. You need it to hold 20*(write_rate in MB/s) > megabytes. E.g. if your array does 100 MB/s, you need a 2000 MB > journal. This calculation is for default gjournal settings. This is usefull info. > > > You could put the journal on another drive or array for best > performance. (Of course, you could skip gjournal and put the WAL on > the other drive). I have the latter, but intent to put this on gjournal too. Axel ---
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B2D25A1-5A0D-4163-A248-E709ADD54CC5>