| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| 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:02:50 |
| Message-ID: | CAMkU=1yQfwuTdGMBYhBWrVAdonN9Dg-TuRfD6Mh4KHbp3BCj3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jun 27, 2018 at 10:01 AM, PG Bug reporting form <
noreply(at)postgresql(dot)org> 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.
>
> I'm using 9.2.18 version.
>
>
That's not a bug. Selects and Updates alone should not block on a pg_dump,
but in conjunction with DROP they certainly can. You can't DROP a table
while it is being dumped, and you can't select from a table while it is
waiting to be dropped.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2018-06-27 18:35:16 | could not read block 0 in file : read only 0 of 8192 bytes when doing nasty on immutable index function |
| Previous Message | Andres Freund | 2018-06-27 15:01:34 | Re: BUG #15253: DROP/select/update query waiting for pg_dump |