| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | "Wolff, Ken L" <ken(dot)l(dot)wolff(at)lmco(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Netapp SnapCenter |
| Date: | 2020-06-26 13:00:49 |
| Message-ID: | 0ECD0414-388A-4DFB-9FCD-1C3D88CAC8CE@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Stephen,
> On 22. Jun, 2020, at 19:00, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> ... and all tablespaces are also on that volume. Basically, anything
> that PG might ever write to needs to all be included in that atomic
> write.
it turns out that tablespaces can be stored on different volumes if you use consistency groups in Netapp to do the snapshots. But this is per documentation that Ken mentioned (see below)! I couldn't verify it as I am not the storage person...
https://www.netapp.com/us/media/tr-4770.pdf
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Hurne | 2020-06-26 13:27:41 | RE: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked |
| Previous Message | Paul Förster | 2020-06-26 12:36:45 | Re: EXTERNAL: Re: Netapp SnapCenter |