X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3207CD1B54E for ; Tue, 6 Apr 2004 05:34:31 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 10955-09 for ; Tue, 6 Apr 2004 05:35:00 -0300 (ADT) Received: from vanessa.inwise.de (Vanessa.inwise.de [62.156.182.8]) by svr1.postgresql.org (Postfix) with ESMTP id F28B3D1B890 for ; Tue, 6 Apr 2004 05:34:13 -0300 (ADT) Received: from juk-15.kraeber.gmbh (Katrin.inwise.de [62.156.182.13]) by vanessa.inwise.de (8.12.11/8.12.11) with ESMTP id i368YuVB027170 for ; Tue, 6 Apr 2004 10:34:56 +0200 From: Torsten Neuer Organization: InWise GmbH - http://www.inwise.de/ To: pgsql-admin@postgresql.org Subject: Re: Raw vs Filesystem Date: Tue, 6 Apr 2004 10:34:54 +0200 User-Agent: KMail/1.6.1 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200404061034.56355.tneuer@inwise.de> X-Scanned-By: milter-sender/0.55.730 (vanessa []); Tue, 06 Apr 2004 10:34:56 +0200 X-Virus-Scanned: by amavis-milter (http://www.amavis.org/) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/85 X-Sequence-Number: 13058 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Dienstag, 30. M=E4rz 2004 06:00 schrieb Christopher Browne: > el_vigia_ec@hotmail.com ("Jaime Casanova") asked: > > so, the real question is what is the best filesystem for optimal speed > > in postgresql? > > The smart-alec answer would be... "Veritas, of course!" > > But seriously, it depends on many factors you have not provided > information about. > > -> Different operating systems support different filesystems; you > should probably specify what OS you are using. > > -> Hardware choices have ENORMOUSLY more impact on speed than any > choice of filesystems. One method for further optimizing access on database files can be to mount = the=20 partition where the database files are kept in a fashion that omits most of= =20 the bookkeeping of the filesystem, e.g. using the -noatime option. Any=20 filesystem that is heavily accessed will greatly benefit from this -=20 especially if the filesystem resides on a RAID 5 disk array since updating= =20 the access times will cause any checksums to be re-computed and written bac= k=20 to the array. hth, Torsten - --=20 InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH Waldhofstra=DFe 14 Tel: +49-4101-403605 D-25474 Ellerbek Fax: +49-4101-403606 E-Mail: info@inwise.de Internet: http://www.inwise.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAcmuunSCI/lmEFI8RAtE+AKDeKS63Yt7fkhiZ3OAH8tj2uXQ7HgCguQ4s 34VyZ5+9Vuum9nmDaDblsSs=3D =3D6B+8 -----END PGP SIGNATURE-----