| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How to configure a read-only database server? |
| Date: | 2011-04-23 16:10:15 |
| Message-ID: | 0B4657E5-134C-409B-B0CC-A801F4299D7E@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Apr 18, 2011, at 6:08 PM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:
> 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
All of those speed up writes. I don't know that they will make any difference at all on a read-only workload.
> * What about wal_level and archive_mode?
Same with these.
>
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-04-23 16:11:38 | Re: Shouldn't we have a way to avoid "risky" plans? |
| Previous Message | Henry | 2011-04-23 15:48:35 | Re: not using partial index |