throwdbaaway

29 ms·

1. 301.▲
   by throwdbaaway 7y ago

   Good point about the "slight" wording, though I don't necessary agree that it can get much worse than 2x, with actual workload that: - could be more I/O bound than when just doing PK lookups with pgbench - could be getti
2. 302.▲
   by throwdbaaway 7y ago

   Thanks for the numbers. Can you run it for -M extended as well? That would be the case when using unnamed prepared statement. Anyway, as there is no way for a query plan cache to be one-size-fit-all, as shown by both TFA and some comments i
3. 303.▲
   by throwdbaaway 7y ago

   Looks like ecto went too far by using named prepared statement by default? Should work just fine with unnamed prepared statement: https://github.com/elixir-ecto/postgrex/blob/master/README.m... Postgres