From: Ron <rjpeace@earthlink.net>
To: Tino Wildenhain <tino@wildenhain.de>
To: pgsql-performance@postgresql.org
Subject: Re: 15,000 tables
Date: Thu, 01 Dec 2005 13:48:11 -0500
Message-ID: <6.2.5.6.0.20051201134344.035fed60@earthlink.net> (raw)
In-Reply-To: <1133462407.5734.43.camel@Andrea.peacock.de>
References: <dmmujf$2rgd$1@news.hub.org>
<Pine.LNX.4.62.0512010609060.2807@qnivq.ynat.uz>
<dmn2lh$maj$1@news.hub.org>
<9A858930-1CA6-4238-92D4-D1E945683653@ehpg.net>
<1133462407.5734.43.camel@Andrea.peacock.de>
Agreed. Also the odds of fs corruption or data loss are higher in a
non journaling fs. Best practice seems to be to use a journaling fs
but to put the fs log on dedicated spindles separate from the actual
fs or pg_xlog.
Ron
At 01:40 PM 12/1/2005, Tino Wildenhain wrote:
>Am Donnerstag, den 01.12.2005, 10:07 -0800 schrieb Gavin M. Roy:
> > Hi Michael,
> >
> > I'm a fan of ReiserFS, and I can be wrong, but I believe using a
> > journaling filesystem for the PgSQL database could be slowing things
> > down.
>
>Have a 200G+ database, someone pulling the power plug
>or a regular reboot after a year or so.
>
>Wait for the fsck to finish.
>
>Now think again :-)
>
>++Tino
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
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: rjpeace@earthlink.net, tino@wildenhain.de
Subject: Re: 15,000 tables
In-Reply-To: <6.2.5.6.0.20051201134344.035fed60@earthlink.net>
* 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