Re: Data directory on read-only media

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Data directory on read-only media
Date: 2005-11-20 20:53:38
Message-ID: 20106.1132520018@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> 5. Don't try to write buffers with commit hint modifications. Just discard
> them.

The performance costs of that alone are astonishing (ie, repeated
verifications of commit status).

I think what you are doing is a completely wrongheaded way to approach
it... it sounds incredibly invasive, messy, and fragile. A database or
tablespace that has been frozen (per VACUUM FREEZE) could sensibly be
put on read-only media, but I can't see doing the rest of this. Have
you thought about putting the more dynamic stuff onto a RAM disk?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2005-11-20 21:01:24 Re: Returning multiple result sets
Previous Message Michael Fuhr 2005-11-20 20:51:11 Plan chosen for PQexecParams