| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Pg_dump |
| Date: | 2023-12-07 18:26:15 |
| Message-ID: | 370989DB-26AD-451A-AF28-C4752E08FE77@elevated-dev.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jason cable | 2023-12-07 18:39:29 | Re: Pg_dump |
| Previous Message | Holger Jakobs | 2023-12-07 18:13:40 | Re: Pg_dump |