3 ms·
Both vacuuming and logical replication are discussed in the article. In particular, vacuuming is easier with InnoDB since the changed records all exist in the r
by stubish 10y ago
Both vacuuming and logical replication are discussed in the article. In particular, vacuuming is easier with InnoDB since the changed records all exist in the redo log whereas PostgreSQL needs to scan the whole table. pglogical is mentioned for people running PG9.4+ as a way of doing minimal downtime cross version upgrades, which wasn't an option back with PG9.2 unless you go with something like slony1 or londiste.
- RedCrowbar 10y ago> vacuuming is easier with InnoDB ... PostgreSQL needs to scan the whole table There's been quite a few improvements to VACUUM in 9.6 [1], including avoiding full-table scans. [1] https://www.postgresql.org/docs/9.6/static/release-9-6.html#AEN129664 https://www.postgresql.org/docs/9.6/static/release-9-6.html#...