4 ms·
But it's only an issue if you rely on lots of transactions for data consistency and my point was that it sounds like they are relying on transactions too much w
by jedberg 10y ago
But it's only an issue if you rely on lots of transactions for data consistency and my point was that it sounds like they are relying on transactions too much which is why they need a more "forgiving" database, which is the part I quoted.
Also they didn't mention anything about the auto vacuumer, which mostly solved the issue they are talking about.
Their lack of mention of the vacuumer and not seeming to know that Postgres supports statement level replication makes me wonder if they took a deep dive into the wrong part of the technology.
- Negitivefrags 10y agoNone of what you said addresses the issue that I (or they) are talking about. On Postgres an update requires a rewrite of every index of the row. On MySQL it only requires an update of the indexes that were touched by the update. If you have a table with 10 indexes then this means doing 10 extra writes physically to the disk.
- dialogbox 10y agoAs I know, not every updates rewrite indexes in PG. It has single page clean up and HOT (heap only tuple) update optimization. Please refer to 64~ page of https://momjian.us/main/writings/pgsql/mvcc.pdf https://momjian.us/main/writings/pgsql/mvcc.pdf.
- continuational 10y ago10 indexes on one table seems a bit much. It sounds like a table that hasn't been normalized.
- stubish 10y agoBoth 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#...