public inbox for [email protected]  

help / color / mirror / Atom feed

From: Scott Ribe <[email protected]>
To: Rajesh Kumar <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Pg_dump
Date: Thu, 7 Dec 2023 11:26:15 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAJk5AtZX23PBG4rfrVt6cp3z_pYGtEE5JvvCRG6Lj3F7=1+C2Q@mail.gmail.com>
	<[email protected]>

> Readers don't block writers, writers don't block readers in PostgreSQL.
> 
> pg_dump is a reader.
> 
> -- 
> Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012

Additionally, I've done some stress testing and found that pg_dump puts surprisingly low load on our dbs. Of course, like everything else, this dependent on your specifics--after all the dump will require reading all rows, so for instance if you're disk-bound, you could see a performance hit. But generally, if your db is running in a reasonably "healthy" performance range and not already close to limits, pg_dump won't have a performance impact visible to users.

view thread (18+ messages)  latest in thread

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Pg_dump
  In-Reply-To: <[email protected]>

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

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