| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 12 draft release notes |
| Date: | 2019-06-13 06:33:48 |
| Message-ID: | 20190613063348.GE1643@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 12, 2019 at 05:25:37PM -0400, Bruce Momjian wrote:
> Since we did not backpatch this fix, I am hesitant to spell out exactly
> how to exploit this DOS attack. Yes, people can read it in the email
> archives, and commit messages, but I don't see the value in spelling it
> out the release notes too.
We could go for a more general version of that, for the reason that it
involves all relations, like:
"A caller of TRUNCATE or VACUUM could previously queue for an access
exclusive lock on a relation it may not have permission to truncate or
vacuum, leading to relations to be blocked from being accessed."
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-13 06:44:43 | Re: Quitting the thes |
| Previous Message | Michael Paquier | 2019-06-13 06:11:15 | Re: [PATCH] vacuumlo: print the number of large objects going to be removed |