JEjeffdavis·Apr 4, 2020
I largely agree, but a couple points I'd like to challenge:
Is hardware corruption really happening and making it into the WAL stream with checksums on?
The next point, on planner hints: it's really just something that hasn't been done. If a few engineers made plans to tackle the problem, a lot could be done in a couple releases' worth of work. In the mean time, people are getting by with various half-measures anyway, such as extensions[1], planner tunables[2], and statistics tweaks[3].
The only dogma is that a half-baked solution isn't wanted. It's got a lot of architectural impact and long-term supportability implications. And a lot of different use cases that need to be considered that may drive different technological solutions. "Make plans stable/managable" is a different use case than "I know something the planner doesn't" which is
Read the rest
different from "Make the planner do this thing because I said so".
[1] https://github.com/ossc-db/pg_hint_plan/blob/master/doc/pg_h...
[2] https://www.postgresql.org/docs/current/runtime-config-query...
[3] https://www.postgresql.org/docs/12/sql-createstatistics.html