From: | "Tyler Mitchell" <TMitchell(at)lignum(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | nicolasb(at)maich(dot)gr |
Subject: | Running postgres on a read-only file system |
Date: | 2002-08-30 20:47:00 |
Message-ID: | OFF16A503E.111A187D-ON88256C25.0071ED03-88256C25.00722457@lignum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, I couldn't get any good answers off the ADMIN list, can you help me?
I haven't been able to finding information on this, or at least I
haven't known the right keywords to search for.
We are trying to make a fully contained, CD-runable version of postgres
for advocacy purposes.
The only problem we are really having is the locking of the database files
in the PGDATA folder. Since the PGDATA folder is going to be on the CD
(i.e. read-only) normal setup prevents us from doing this. We indeed, only
want to read data and not write.
Can you direct me to either other resources to read or at least point me to
the settings/functionality that I need to learn more about? Or better yet
could you give me some guidance on how to get around this. The simpler the
solution the better (i.e. postmaster
options, environment variables, etc.).
Is it possible somehow?
Tyler
p.s. We are testing this on a windows beta but I hope that doesn't make a
difference.
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-08-30 20:48:33 | Re: Accessing original TupleDesc from SRF |
Previous Message | Joe Conway | 2002-08-30 20:18:30 | Re: SRF memory mgmt patch (was [HACKERS] Concern about |