| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: VACUUM FULL results in deadlock |
| Date: | 2019-07-05 13:31:08 |
| Message-ID: | CA+TgmoaewCKsDz+X0=j+h9uWGab1pH=4TG7KnfFt6u9FyL7sEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jul 5, 2019 at 9:27 AM Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> wrote:
> Thanks for your comment! I can also reproduce deadlocks for other
> statements that operate on distinct databases, at least also for
> ANALYZE. The documentation states that such statements operate on
> their current databases. If this is not a bug, should maybe the
> documentation be updated to mention this caveat?
Possibly. The trick is always to find a good place to put things like
this -- they need to not consume a disproportionate amount of space
relative to the importance of an issue, and they need to be inserted
into a place in the documentation where they make logical sense and
are likely to be seen by users. If you have a good idea, feel free to
submit a patch, perhaps on pgsql-docs.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-07-05 13:33:27 | Re: BUG #15886: I cannot install postgres |
| Previous Message | Manuel Rigger | 2019-07-05 13:26:45 | Re: VACUUM FULL results in deadlock |