3 ms·
That's weird, what's your checkpoint_timeout? The default is 5 minutes, so you certainly shouldn't be pushing to S3 every 10s if the DB is idle. Apparently PG
by icebraining 10y ago
That's weird, what's your checkpoint_timeout? The default is 5 minutes, so you certainly shouldn't be pushing to S3 every 10s if the DB is idle.
Apparently PG 10 will improve your use case, though: http://paquier.xyz/postgresql-2/postgres-10-checkpoint-skip/ http://paquier.xyz/postgresql-2/postgres-10-checkpoint-skip/
EDIT: Also, wal-e compresses by default, so even those regular WAL files should be much smaller than 10MB. Are you sure the DB is really idle?
- user5994461 10y agoThere is a setting for the time interval. That's not the point. I'm not gonna delay replication and backup by minutes just because the replication system sucks. I'd rather pay the storage for my use case. Compression is enabled indeed. Surprisingly, the compression ratio for "nothing going on" is terrible. (still multiple MBytes). The next version of postgre will redo the transaction log to have dynamic adaptive sizing, with new settings to control it. Not there yet.
- icebraining 10y agoAFAIK the dynamic WAL sizing has already landed in 9.5: http://www.databasesoup.com/2016/01/configuration-changes-in-95-transaction.html http://www.databasesoup.com/2016/01/configuration-changes-in... Or is this something else you're talking about?
- user5994461 10y agoYes, I'm talking about that and it's in 9.5 (which was released recently)