pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mladen Gogala <gogala.mladen@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: postgres large database backup
Date: Thu, 1 Dec 2022 08:47:39 -0500
Message-ID: <d901c987-76e5-873e-2e5d-b358535b11b2@gmail.com> (raw)
In-Reply-To: <31e934ad-5e3e-22d4-f8b1-0fdee463eb42@gmail.com>
References: <CA+ONtZ7CdiJ2X8x_8sPHR+tz-vv7mR1uoDzLia3fzWVZA9k0JQ@mail.gmail.com>
	<9d50f118-a3dd-565a-41bd-d3056b9b90d6@gmail.com>
	<592a2c79-9728-e450-ad60-a0df7dd0f214@erven.at>
	<303273b8-6116-23b2-f26d-866e38ef1c0a@gmail.com>
	<CAHDg04u0jMySKG+dN_+zpGa=_fAT-rZ2XpQPR_rOVKS7FOHMXQ@mail.gmail.com>
	<31e934ad-5e3e-22d4-f8b1-0fdee463eb42@gmail.com>

On 11/30/22 20:51, Ron wrote:
> ZFS will yes be slower than a raw disk (but that’s not an option for 
> Pg anyway), and may or may not be faster than a different  filesystem 
> on a HW RAID volume or storage array volume. It absolutely takes more 
> care/clue/tuning to get Pg write performance on ZFS, and ZFS does 
> duplicate some of Pg’s resiliency so there is duplicate work going on.

Ron, if this raw device reference is about ASM, Oracle has a file system 
on top of ASM, called ACFS, and I have been able to run PostgreSQL on 
top of ACFS. The reason to do that is redundancy. ASM/ACFS with 
PostgreSQL behaves similarly to Veritas Cluster, when one Postgres 
cluster goes down, the other one is started. And you don't have to pay 
for it, unless you start using storage snapshots. That ACFS feature 
requires a commercial license.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

view thread (18+ messages)  latest in thread

Message-ID: <d901c987-76e5-873e-2e5d-b358535b11b2@gmail.com>
Permalink:  ../d901c987-76e5-873e-2e5d-b358535b11b2@gmail.com/
Also on:    postgresql.org/message-id/d901c987-76e5-873e-2e5d-b358535b11b2@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: gogala.mladen@gmail.com
  Subject: Re: postgres large database backup
  In-Reply-To: <d901c987-76e5-873e-2e5d-b358535b11b2@gmail.com>
  References: <CA+ONtZ7CdiJ2X8x_8sPHR+tz-vv7mR1uoDzLia3fzWVZA9k0JQ@mail.gmail.com> <9d50f118-a3dd-565a-41bd-d3056b9b90d6@gmail.com> <592a2c79-9728-e450-ad60-a0df7dd0f214@erven.at> <303273b8-6116-23b2-f26d-866e38ef1c0a@gmail.com> <CAHDg04u0jMySKG+dN_+zpGa=_fAT-rZ2XpQPR_rOVKS7FOHMXQ@mail.gmail.com> <31e934ad-5e3e-22d4-f8b1-0fdee463eb42@gmail.com> <d901c987-76e5-873e-2e5d-b358535b11b2@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox