Re: How to prioritise walsender reading from pg_wal over WAL writes?

I would first determine where the bottleneck is. Is it really the walsender, or is it on the network or in the standby server's replay? It is really the walsender, and it really is the performance of the WAL storage on the master. Check the difference between "sent_lsn", "replay_lsn" from

Re: Postgres using nested loops despite setting enable_nestloop to false

I found out that setting: set join_collapse_limit = 14; set from_collapse_limit = 14; In addition to disabling the nested loops does produce a viable plan, with only the nested loop to generate the tijd table cross join as a basic part down low... The original values for those were 12. It does seem