Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools? - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
Date
Msg-id CABUevExTcY=zQqh=nhUJrpPZYr7Cf9DeBmpH0oUPaURjGv0RgA@mail.gmail.com
Whole thread Raw
In response to Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?  (HECTOR INGERTO <HECTOR_25E@hotmail.com>)
Responses RE: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?
List pgsql-general
On Sun, Jan 15, 2023 at 10:57 PM HECTOR INGERTO <hector_25e@hotmail.com> wrote:

 

> But you cannot and should not rely on snapshots alone

 

That’s only for non atomic (multiple pools) snapshots. Isn’t?


Right. For single-filesystem installs it should be fine. Just make sure it has both the data and the WAL directories in the same one.


 

If I need to rely only on ZFS (automated) snapshots, then the best option would be to have two DB? Each one in each own pool. One HDD DB and one SSD DB. Then, the backend code should know on which DB the requested data is. 


 You could. I wouldn't -- I would set it up to use proper backups instead, maybe using snapshots as the infrastructure. That gives you other advantages as well, like being able to do PITR. It's a little more to set up, but I'd say it's worth it.

//Magnus

pgsql-general by date:

Previous
From: pf@pfortin.com
Date:
Subject: Re: pg_upgrade 13.6 to 15.1?
Next
From: Alan Hodgson
Date:
Subject: Re: pg_upgrade 13.6 to 15.1?