| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, "Wolff, Ken L" <ken(dot)l(dot)wolff(at)lmco(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: EXTERNAL: Re: Netapp SnapCenter |
| Date: | 2020-06-29 15:18:24 |
| Message-ID: | 882B0286-E42F-4B86-AF06-BAC4734E6304@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Stephen,
> On 29. Jun, 2020, at 16:43, Stephen Frost <sfrost(at)snowman(dot)net> 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 quiescing the database.
ah, so it's more like freezing. Thanks.
> 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 v12 was released isn't going to
> work with those changes.
we have 11.6 and 12.3. 11.6 because we (unfortunately) have to use Qlik (formerly Attunity). And no, that again wasn't my decision. Databases which are involved in Qlik replication can't be updated (yet) according to our Qlik specialist. I had a big argument with him when I updated even from 11.5 to 11.6. This means I can't even update to 11.8.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-06-29 15:29:52 | Re: EXTERNAL: Re: Netapp SnapCenter |
| Previous Message | Brajendra Pratap Singh | 2020-06-29 15:12:56 | Re: Postgresql HA Cluster |