Re: Proposal: add a debug message about using geqo

ws=630 width=36) (actual time=0.014..0.016 rows=3 loops=1) Settings: geqo_threshold = '16' GeqoDetails: GEQO: not used, geqo_threshold: 16, Max join nodes: 3 Planning Time: 0.516 ms Execution Time: 0.190 ms (24 rows) > On Tue, May 10, 2022 at 6:35 AM KAWAMOTO Masaya wrote: > > &

Proposal: add a debug message about using geqo

planning or GEQO. - When tuning PostgreSQL, user can determine the suitable value of geqo_threshold parameter. Best regards. -- KAWAMOTO Masaya SRA OSS, Inc. Japan debugmessage_about_geqo.patch Description: Binary data

Re: Typo in pgbench messages.

; " INT64_FORMAT "/" INT64_FORMAT " (%.3f %%)\n", > > + printf("number of transactions above the %.1f ms latency limit: > > " INT64_FORMAT "/" INT64_FORMAT " (%.3f%%)\n", > > latency_limit / 1000.0, latency_late, ntx,

Typo in pgbench messages.

ns above the %.1f ms latency limit: " INT64_FORMAT "/" INT64_FORMAT " (%.3f %%)\n", + printf("number of transactions above the %.1f ms latency limit: " INT64_FORMAT "/" INT64_FORMAT " (%.3f%%)\n", latency_limit / 1000.0, latency_late, ntx, (ntx > 0) ? 100.0 * latency_late / ntx : 0.0); -- KAWAMOTO Masaya SRA OSS, Inc. Japan