Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3BE291337B82 for ; Tue, 19 Apr 2011 04:51:22 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 11137-04 for ; Tue, 19 Apr 2011 07:51:03 +0000 (UTC) X-Greylist: delayed 00:06:01.451492 by SQLgrey-1.7.6 Received: from mail.edd.fr (mail.edd.fr [62.23.156.6]) by mail.postgresql.org (Postfix) with ESMTP id 6EA10133740B for ; Tue, 19 Apr 2011 04:51:03 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mail.edd.fr (Postfix) with ESMTP id 314E8D01BA for ; Tue, 19 Apr 2011 09:45:00 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at vs-mailrelay.intranet Received: from mail.edd.fr ([127.0.0.1]) by localhost (vs-mailrelay.intranet [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0sYWZCrkCysY for ; Tue, 19 Apr 2011 09:45:00 +0200 (CEST) Received: from vs-dovecot.intranet (vs_dovecot.intranet [192.168.39.143]) by mail.edd.fr (Postfix) with ESMTP id 01205D007B for ; Tue, 19 Apr 2011 09:45:00 +0200 (CEST) Received: from [192.168.13.113] (primbault.intranet [192.168.13.113]) by vs-dovecot.intranet (Postfix) with ESMTP id D81DA20622 for ; Tue, 19 Apr 2011 09:44:59 +0200 (CEST) Message-ID: <4DAD3DB4.2040501@rimbault.org> Date: Tue, 19 Apr 2011 09:45:56 +0200 From: philippe User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101213 Iceowl/1.0b2 Icedove/3.1.7 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: How to configure a read-only database server? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201104/275 X-Sequence-Number: 43337 hi, Perhaps in postgresql.conf : default_transaction_read_only regards philippe Le 19/04/2011 00:08, Stefan Keller a écrit : > I browsed the faq and looked at PostgreSQL performance books but I > could not find the obvious: > How to configure a read-only database server? > > I have a single-disk virtual Linux system and a read-only dataset > which is exposed to internet and completely replaced from time to > time. > > This is what I found so far: > > * Disabling autovacuum daemon. > * Setting postgresql.conf parameters: > fsync=off > synchronous_commit=off > full_page_writes=off > > * For the session: > SET transaction_read_only TO FALSE; > SET TRANSACTION READ ONLY; > > * What about wal_level and archive_mode? > > => Any comments on speeding up/optimizing such database server? > > Yours, Stefan >