| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
| Cc: | Shaw Terwilliger <sterwill(at)sourcegear(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL over NFS? |
| Date: | 2001-02-10 00:42:12 |
| Message-ID: | 200102100042.TAA01323@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> The part about cache incoherency is very true, the _only_ cache coherency
> NFS offers is _only_ in the v3 spec, and is specifically called 'wcc'
> 'weak cache coherency' (afaik). So yes, you can expect differnent
> NFS clients to get different inconsistant views on heavily modified
> files unless they use advisory locking (which should fsync out locked
> ranges before release).
>
> Anyhow, if the idea is just to get a nice backup system, you could
> do a pg_dump and write the output to a NFS mounted FS, there's probably
> less that can go wrong with a large sequencial write than heavy shared
> read/write/seek.
Or just rsh over to the database system and pipe the output back to the
'backup' machine.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Castle | 2001-02-10 00:42:53 | Re: PostgreSQL over NFS? |
| Previous Message | tc lewis | 2001-02-10 00:37:05 | Re: Re: PostgreSQL over NFS? |