From: | jason cable <cablej2082(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, 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:39:29 |
Message-ID: | LV3P222MB09852463EF05D3AF0CC37C2AF08BA@LV3P222MB0985.NAMP222.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
That happens to me too the last time I took dump
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Sent: Thursday, December 7, 2023 10:26:15 AM
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
> 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 | Tom Lane | 2023-12-07 18:52:49 | Re: Pg_dump |
Previous Message | Scott Ribe | 2023-12-07 18:26:15 | Re: Pg_dump |