Re: PG 12 draft release notes - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PG 12 draft release notes
Date
Msg-id 20190613131108.h6vyspdntj5cw5fg@momjian.us
Whole thread Raw
In response to Re: PG 12 draft release notes  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PG 12 draft release notes
List pgsql-hackers
On Thu, Jun 13, 2019 at 03:33:48PM +0900, Michael Paquier wrote:
> 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."

Uh, that still seems to suggest an attack and I am not sure that
information is very useful to users.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Improve handling of pg_stat_statements handling of bind "IN" variables
Next
From: Bruce Momjian
Date:
Subject: Re: PG 12 draft release notes