Re: PG 12 draft release notes

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Michael Paquier <michael@paquier.xyz>

Cc: Ian Barwick <ian.barwick@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2019-06-13T13:12:58Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

doc: PG 12 relnotes: update wording on truncate/vacuum item
- 4f41a7227511 12.0 landed
docs: PG 12 relnotes, update btree items
- 4bfb79ff6b1f 12.0 landed
doc: PG 12 relnotes, list added snowball/FTS languages
- 968072837173 12.0 landed
doc: PG 12 relnotes, merge new SQL partition function items
- 6a631a454664 12.0 landed
docs: PG 12 release notes, support functions
- 728840fe13ac 12.0 landed
docs: PG 12 relnote adjustments based on feedback from Tom Lane
- 8e719d33fd25 12.0 landed
docs: adjust RECORD PG 12 relnote item
- 3468a04a3e49 12.0 landed
doc: adjust PG 12 relnotes item on float digit adjustment
- b84a801d6a67 12.0 landed
doc: adjustments for PG 12 release notes
- 32fe2e3194c7 12.0 landed
docs: fix duplicate wording in PG 12 release notes
- 34d40becfa7a 12.0 landed
doc: properly attibute PG 12 pgbench release note item
- 5d971565a799 12.0 landed
doc: PG 12 release notes: normalize attribution names
- f86b0c3c4653 12.0 landed
Refactor the fsync queue for wider use.
- 3eb77eba5a51 12.0 cited
Add "split after new tuple" nbtree optimization.
- f21668f328c8 12.0 cited
Add nbtree high key "continuescan" optimization.
- 29b64d1de7c7 12.0 cited
Allow amcheck to re-find tuples using new search.
- c1afd175b5b2 12.0 cited
Consider secondary factors during nbtree splits.
- fab250243387 12.0 cited
Partial implementation of SQL/JSON path language
- 72b6460336e8 12.0 cited
Allow extensions to generate lossy index conditions.
- 74dfe58a5927 12.0 cited
Make TupleTableSlots extensible, finish split of existing slot type.
- 4da597edf1ba 12.0 cited
Reduce path length for locking leaf B-tree pages during insertion
- d2086b08b023 12.0 cited

On Thu, Jun 13, 2019 at 09:11:08AM -0400, Bruce Momjian wrote:
> 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.

I went with this wording:

        This prevents unauthorized locking, which could interfere with
        user queries.

-- 
  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 +