pgsql: Trigger autovacuum based on number of INSERTs

2020-03-27 Thread David Rowley
Trigger autovacuum based on number of INSERTs Traditionally autovacuum has only ever invoked a worker based on the estimated number of dead tuples in a table and for anti-wraparound purposes. For the latter, with certain classes of tables such as insert-only tables, anti-wraparound vacuums could b

pgsql: Justify nbtree page split locking in code comment.

2020-03-27 Thread Peter Geoghegan
Justify nbtree page split locking in code comment. Delaying unlocking the right child page until after the point that the left child's parent page has been refound is no longer truly necessary. Commit 40dae7ec made nbtree tolerant of interrupted page splits. VACUUM was taught to avoid deleting a

pgsql: Allow walreceiver configuration to change on reload

2020-03-27 Thread Alvaro Herrera
Allow walreceiver configuration to change on reload The parameters primary_conninfo, primary_slot_name and wal_receiver_create_temp_slot can now be changed with a simple "reload" signal, no longer requiring a server restart. This is achieved by signalling the walreceiver process to terminate and

pgsql: Set wal_receiver_create_temp_slot PGC_POSTMASTER

2020-03-27 Thread Alvaro Herrera
Set wal_receiver_create_temp_slot PGC_POSTMASTER Commit 329730827848 gave walreceiver the ability to create and use a temporary replication slot, and made it controllable by a GUC (enabled by default) that can be changed with SIGHUP. That's useful but has two problems: one, it's possible to cause

pgsql: Rearrange validity checks for plpgsql "simple" expressions.

2020-03-27 Thread Tom Lane
Rearrange validity checks for plpgsql "simple" expressions. Buildfarm experience shows what probably should've occurred to me before: if a cache flush occurs partway through building a generic plan, then the plansource may have is_valid = false even though the plan is valid. We need to accept this

pgsql: Update SQL features

2020-03-27 Thread Peter Eisentraut
Update SQL features Change F311 to supported. This was already accomplished when subfeature F311-04 (WITH CHECK OPTION) was added, but the top-level feature wasn't updated at the time. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/8d1b9648c5861dd14773e551f0b0f37f