From: | philippe <pg(at)rimbault(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to configure a read-only database server? |
Date: | 2011-04-19 07:45:56 |
Message-ID: | 4DAD3DB4.2040501@rimbault.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Klemme | 2011-04-19 08:24:18 | Re: big distinct clause vs. group by |
Previous Message | Stefan Keller | 2011-04-18 22:08:38 | How to configure a read-only database server? |