[PERFORM] WAL still kept in pg_xlog even long after heavy workload is done

Hello, We're encountering some problems with WAL growth in production with PostgreSQL 9.6.3 and 9.6.2. From what I know a WAL file can either be recycled(and would be reused) or deleted. We'd like to have better control over the amount of WAL that is kept around. There were a few occasions where

Re: [PERFORM] WAL still kept in pg_xlog even long after heavy workload is done

To get the values right, you have to consider the "unit" column in pg_settings. On mine, it is 16M for both min and max wal size. So it would be 1024 x 1024 x 16 x (pg_settings.min_wal_size or pg_settings.max_wal_size) The result of this formula should be close to what you specified in

[PERFORM] Row-level security performance

Hi, I see in the v10 release notes (2017-10-05) that there's been a change to "Improve performance of queries affected by row-level security restrictions". I am using RLS in a Postgres 9.5 database and am seeing some very bad performance when joining tables. Upgrading this DB to v10 shows a