| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Janet Jacobsen <jsjacobsen(at)lbl(dot)gov> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: change location of postmaster.pid file? |
| Date: | 2009-07-10 22:43:18 |
| Message-ID: | 407d949e0907101543q590f748dhb6b04ce74c373344@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jul 10, 2009 at 11:17 PM, Janet Jacobsen<jsjacobsen(at)lbl(dot)gov> wrote:
> Is it possible to create a database cluster on a machine that
> has write access to the shared file system, shut down the
> Postgres server on that machine, and then start up the
> Postgres server on the machine that cannot write to the
> shared file system, and thereafter, *only query* the database.
Postgres isn't really designed to work this way. It expects to have
write access and will occasionally still write stuff to disk even for
read-only queries.
It won't work even a little bit before 8.3. For 8.3 or later you could
maybe make it work using vacuum freeze but there's no facility to
verify that it's really frozen everything and you'll still be taken by
surprise by queries which try to use temporary space for large sorts
or commands which start transactions that you didn't realize were
necessary.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-07-10 22:48:30 | Re: BR/ |
| Previous Message | Tom Lane | 2009-07-10 22:42:36 | Re: change location of postmaster.pid file? |