A Hairy PostgreSQL Incident by ardentperf.com


Unlike some other relational databases, PostgreSQL does not give much visibility into execution plans used at runtime. There’s auto_explain which can log actual plans for SQL that successfully completes with a runtime above some threshold. (View Highlight)

Joshua left a comment reminding me about Cybertec and Hironobu Suzuki’s extension pg_show_plans. (View Highlight)

We have a script of our own which is very similar to Tanel Poder’s run_xcpu.sh in his 0x.tools collection. (View Highlight)

Note: `run_xcpu.sh` in his [0x.tools collection](https://0x.tools/)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s