| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | sennirban89(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15253: DROP/select/update query waiting for pg_dump |
| Date: | 2018-06-27 15:01:34 |
| Message-ID: | 20180627150134.lphsddetwachkrkj@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2018-06-27 14:01:09 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15253
> Logged by: NIRBAN SEN
> Email address: sennirban89(at)gmail(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: rhel7
> Description:
>
> DROP/select/update queries are going into waiting state when pg_dump is
> running.
DROP TABLE, and many other kinds of DDL, are indeed going to be blocked
by a concurrent pg_dump. That's expected and not a bug. SELECT / UPDATE
on their own won't.
Please note that the form you used is for reporting a bug, but I do not
see one in your report?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2018-06-27 15:02:50 | Re: BUG #15253: DROP/select/update query waiting for pg_dump |
| Previous Message | PG Bug reporting form | 2018-06-27 14:01:09 | BUG #15253: DROP/select/update query waiting for pg_dump |