Horton

Re: PG 14 release notes, first draft

Joe Conway <mail@joeconway.com>

View thread View on postgr.es
From: Joe Conway <mail@joeconway.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-05-11T15:26:48Z
Lists: pgsql-hackers 
On 5/11/21 11:11 AM, Bruce Momjian wrote:
> On Tue, May 11, 2021 at 06:57:19AM -0400, Joe Conway wrote:
>> On 5/10/21 9:56 PM, Bruce Momjian wrote:
>> > On Mon, May 10, 2021 at 07:50:14AM -0400, Joe Conway wrote:
>> > > On 5/10/21 2:03 AM, Bruce Momjian wrote:
>> > > > I have committed the first draft of the PG 14 release notes.  You can
>> > > > see the most current  build of them here:
>> > > > > 	https://momjian.us/pgsql_docs/release-14.html
>> > > > > I need clarification on many items, and the document still needs
>> > > its
>> > > > items properly ordered, and markup added.  I also expect a lot of
>> > > > feedback.
>> > > > > I plan to work on completing this document this coming week in
>> > > > preparation for beta next week.
>> > > 
>> > > While only a small change, this commit does affect user visible behavior and
>> > > so should probably be noted:
>> > > 
>> > > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b12bd4869b5e
>> > 
>> > I see your point.  Here is the release entry I added:
>> 
>> Not quite -- maybe something like the below:
>> 
>> > 	<para>
>> > 	Return false for has_column_privilege() checks on non-existent or dropped columns (Joe Conway)
>> 
>> Always return NULL for has_column_privilege() checks on non-existent or
>> dropped column by attnum (Joe Conway)
>> 
>> > 	<para>
>> > 	Previously such columns returned an invalid column error.
>> 
>> Previously existence of such columns were ignored when caller had table
>> level privileges.
> 
> I can't reproduce the NULL using column name text:

> 	test=> SELECT has_column_privilege('test', 'z', 'SELECT');
> 	ERROR:  column "z" of relation "test" does not exist

That is the way it is supposed to work when the column is specified by 
name. The patch did not change that in any way.

> but I was able to show it using attribute numbers, as you explained:

Yes, that was what the patch fixed.

Joe

-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

Commits

  1. doc: add mention of +4GB windows file handling in PG14 relnotes

  2. doc: PG 14 relnotes fixes

  3. doc: PG 14 relnote updates

  4. doc: PG 14 relnotes, adjust pg_{read|write}_all_data entry

  5. Update PG 14 relnotes for vacuum_cost_page_miss

  6. doc: update PG 14 release notes with recent feedback

  7. Update replication statistics after every stream/spill.

  8. Add information of total data processed to replication slot stats.

  9. Use NameData datatype for slotname in stats.

  10. Add back vacuum_cleanup_index_scale_factor parameter.

  11. Don't consider newly inserted tuples in nbtree VACUUM.

  12. pgbench: Improve time logic.

  13. Track total amounts of times spent writing and syncing WAL data to disk.

  14. Allow decoding at prepare time in ReorderBuffer.

  15. Extend the output plugin API to allow decoding of prepared xacts.

  16. Fix nbtree cleanup-only VACUUM stats inaccuracies.

  17. Execute invalidation messages for each XLOG_XACT_INVALIDATIONS message

  18. Fix our Windows stat() emulation to handle file sizes > 4GB.

  19. Trigger autovacuum based on number of INSERTs

  20. Speed up planning when partitions can be pruned at plan time.

  21. Remove support for password_encryption='off' / 'plain'.

  22. Increase work_mem and maintenance_work_mem defaults by 4x