From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | shiwangini(dot)shishulkar(at)webgility(dot)com |
Subject: | BUG #15965: During Backup:- Unable to Perform DDL and DML on postgres DB |
Date: | 2019-08-19 12:22:17 |
Message-ID: | 15965-413bf5d18aaeface@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15965
Logged by: Shiwangini Shishulkar
Email address: shiwangini(dot)shishulkar(at)webgility(dot)com
PostgreSQL version: 11.4
Operating system: CentOS Linux release 7.6.1810 (Core)
Description:
It was kind of very strange behavior, I have observed so far. we have 69GB
PROD database and during it's backup , I can't perform any DDL and DML on
postgres database. Only 'select' statements I can run. The database takes
~45minutes for backup. Below statement I'm running for backup:
pg_dump -U postgres -d wg -f wg.sql
Looks like pg_dump locks all tables of database during backup window. Any
other way/command to take backup? Also, I have seen that postmaster CPU
utilization reaches 100% when pg_dump backup running on. Any way to avoid
this.
I have also set priority of backup script by 'nice - 18 backup.sh' , but
when backup starts postmaster gets kicked off and cause 100% CPU
utilization. Any way to avoid this?
Please get back to me in case of any query. Please try to look into this on
priority since this is happening on PROD.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2019-08-19 13:22:37 | BUG #15966: Docs: |
Previous Message | Arthur Zakirov | 2019-08-19 09:40:05 | Re: BUG #15961: psql should be able to read password from stdin |