Re: PG 12 draft release notes

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Ian Barwick <ian.barwick@2ndquadrant.com>

Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2019-05-22T07:26:51Z

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 Wed, May 22, 2019 at 09:19:53AM +0900, Ian Barwick wrote:
> the last two items are performance improvements not related to authentication;
> presumably the VACUUM item would be better off in the "Utility Commands"
> section and the TRUNCATE item in "General Performance"?

I agree with removing them from authentication, but these are not
performance-related items.  Instead I think that "Utility commands" is
a place where they can live better.

I am wondering if we should insist on the DOS attacks on a server, as
non-authorized users are basically able to block any tables, and
authorization is only a part of it, one of the worst parts
actually...  Anyway, I think that "This prevents unauthorized locking
delays." does not provide enough details.  What about reusing the
first paragraph of the commits?  Here is an idea:
"A caller of TRUNCATE/VACUUM/ANALYZE could previously queue for an
access exclusive lock on a relation it may not have permission to
truncate/vacuum/analyze, potentially interfering with users authorized
to work on it.  This could prevent users from accessing some relations
they have access to, in some cases preventing authentication if a
critical catalog relation was blocked."
--
Michael