Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-29 Thread Paul Förster
Hi Stephen, > On 29. Jun, 2020, at 17:29, Stephen Frost wrote: > > I typically recommend rather strongly against using anything that won't > allow you to update to keep pace with PG minor versions, considering > they include critical security and corruption fixes (in some cases, but > even if th

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-29 Thread Stephen Frost
Greetings, * Paul Förster (paul.foers...@gmail.com) wrote: > > On 29. Jun, 2020, at 16:43, Stephen Frost wrote: > > I certainly don't blame you, particularly given all the changes > > regarding how restore is done which went into v12- obviously anything > > that hasn't been updated since before v

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-29 Thread Paul Förster
Hi Stephen, > On 29. Jun, 2020, at 16:43, Stephen Frost wrote: > > On some database platforms it basically means "stop writing", in order > to allow a backup to be taken, but that's not what happens on PG and any > documentation about using PG's start/stop definitely shouldn't be > talking about

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-29 Thread Stephen Frost
Greetings, * Paul Förster (paul.foers...@gmail.com) wrote: > > On 29. Jun, 2020, at 15:32, Stephen Frost wrote: > > > > Presumably they mean 'quiesce', except that that *isn't* what PG's > > yes, sorry, "quiece" was a typo on my part. I never fully understood what > they mean with "quiesce" an

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-29 Thread Paul Förster
Hi Stephen, > On 29. Jun, 2020, at 15:32, Stephen Frost wrote: > > Presumably they mean 'quiesce', except that that *isn't* what PG's yes, sorry, "quiece" was a typo on my part. I never fully understood what they mean with "quiesce" anyway. But then, I'm not the storage specialist in out comp

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-29 Thread Stephen Frost
Greetings, * Paul Förster (paul.foers...@gmail.com) wrote: > > On 26. Jun, 2020, at 12:29, Magnus Hagander wrote: > > I believe NetApp does atomic snapshots across multiple volumes, if you have > > them in the same consistency group. (If you don't then you're definitely in > > for a world of pa

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-26 Thread Paul Förster
Hi Magnus, > On 26. Jun, 2020, at 12:29, Magnus Hagander wrote: > I believe NetApp does atomic snapshots across multiple volumes, if you have > them in the same consistency group. (If you don't then you're definitely in > for a world of pain if you ever have to restore) > > Snapshotting multip

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-26 Thread Magnus Hagander
On Thu, Jun 25, 2020 at 5:23 PM Paul Förster wrote: > Hi Ken, > > > On 25. Jun, 2020, at 17:15, Wolff, Ken L 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 re

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-25 Thread David G. Johnston
On Thu, Jun 25, 2020 at 8:24 AM Paul Förster wrote: > Archived WAL is another thing, but PGDATA and pg_wal should IMHO always be > located on the same volume, along with tablespaces, if any. > My understanding that having such a setup (single volume) eases administration at the cost of performan

Re: EXTERNAL: Re: Netapp SnapCenter

2020-06-25 Thread Paul Förster
Hi Ken, > On 25. Jun, 2020, at 17:15, Wolff, Ken L 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 se

RE: EXTERNAL: Re: Netapp SnapCenter

2020-06-25 Thread Wolff, Ken L
>> On 23. Jun, 2020, at 22:59, Wolff, Ken L wrote: >> >> https://www.netapp.com/us/media/tr-4770.pdf > I will check this out. Thank you very much. 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 specif