Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cf/5330~1
Choose a base ref
...
head repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cf/5330
Choose a head ref
  • 2 commits
  • 22 files changed
  • 2 contributors

Commits on May 18, 2025

  1. Add function to log the plan of the currently running query 

    Currently, we have to wait for the query execution to finish
to know its plan either using EXPLAIN ANALYZE or auto_explain.
This is not so convenient, for example when investigating
long-running queries on production environments.
To improve this situation, this  adds pg_log_query_plan()
function that requests to log the plan of the currently
executing query.

On receipt of the request, codes for logging plan is wrapped
to every ExecProcNode and when the executor runs one of
ExecProcNode, the plan is actually logged. These wrappers are
unwrapped when once the plan is logged.
In this way, we can avoid adding the overhead which we'll face
when adding CHECK_FOR_INTERRUPTS() like mechanisms in somewhere
in executor codes safely.

By default, only superusers are allowed to request to log the
plans because allowing any users to issue this request at an
unbounded rate would cause lots of log messages and which can
lead to denial of service.
    Atsushi Torikoshi authored and Commitfest Bot committedMay 18, 2025
    Configuration menu
    Copy the full SHA
    4910c04View commit details
    Browse the repository at this point in the history

  2. [CF 5330] v44 - Logging plan of the currently running query 

    This branch was automatically generated by a robot using es from an
email thread registered at:

https://commitfest.postgresql.org//5330

The branch will be overwritten each time a new  version is posted to
the thread, and also periodically to check for bitrot caused by changes
on the master branch.

(es): https://www.postgresql.org/message-id/[email protected]
Author(s): Atsushi Torikoshi
    Commitfest Bot committedMay 18, 2025
    Configuration menu
    Copy the full SHA
    a8da3f6View commit details
    Browse the repository at this point in the history
Loading