| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | "Wolff, Ken L" <ken(dot)l(dot)wolff(at)lmco(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: EXTERNAL: Re: Netapp SnapCenter |
| Date: | 2020-06-25 15:23:52 |
| Message-ID: | B21728B2-397F-4A94-83B7-AF0DD5C382D3@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Ken,
> On 25. Jun, 2020, at 17:15, Wolff, Ken L <ken(dot)l(dot)wolff(at)lmco(dot)com> wrote:
> There's actually a lot of good stuff in that document about Postgres in general. I'd be curious to hear what everyone thinks, though, and specifically about what NetApp recommends in Section 3.3 about putting data and WAL on separate volumes, which I believe contradicts what's been discussed in this email thread.
yes, I've read the part about different volumes and I must say, I don't agree because I think it violates atomicity.
Archived WAL is another thing, but PGDATA and pg_wal should IMHO always be located on the same volume, along with tablespaces, if any.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-06-25 15:32:39 | Re: EXTERNAL: Re: Netapp SnapCenter |
| Previous Message | Wolff, Ken L | 2020-06-25 15:15:07 | RE: EXTERNAL: Re: Netapp SnapCenter |