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: af0c248
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: 377a142
Choose a head ref
  • 2 commits
  • 36 files changed
  • 2 contributors

Commits on Apr 1, 2025

  1. Proposal for progressive explains 

    This proposal introduces a feature to print execution plans of active
queries in an in-memory shared DSA so that other sessions can visualize
via new view pg_stat_progress_explain.

Plans are only printed if new GUC parameter progressive_explain is
enabled.

When new GUC progressive_explain_interval is set to 0 the plan will be
printed only at query start. If set to any other value the QueryDesc
will be adjusted adding instrumentation flags. In that case the plan
will be printed on a fixed interval controlled by progressive_explain_interval
including all instrumentation stats computed so far (per node rows and
execution time).

New view:
- pg_stat_progress_explain
  - datid: OID of the database
  - datname: Name of the database
  - pid: PID of the process running the query
  - last_update: timestamp when plan was last printed
  - query_plan: the actual plan (limited read privileges)

New GUCs:
- progressive_explain: if progressive plans are printed for local
session.
  - type: bool
  - default: off
  - context: user
- progressive_explain_interval: interval between each explain print.
  - type: int
  - default: 0
  - min: 0
  - context: user
- progressive_explain_format: format used to print the plans.
  - type: enum
  - default: text
  - values: [TEXT, XML, JSON, or YAML]
  - context: user
- progressive_explain_settings: controls whether information about
modified configuration is added to the printed plan.
  - type: bool
  - default: off
  - context: user
- progressive_explain_verbose: controls whether verbose details are
added to the printed plan.
  - type: bool
  - default: off
  - context: user
- progressive_explain_buffers: controls whether buffers details are
added to the printed plan.
  - type: bool
  - default: off
  - context: user
- progressive_explain_timing: controls whether per node timing details
are added to the printed plan.
  - type: bool
  - default: true
  - context: user
- progressive_explain_wal: controls whether WAL record generation
details are added to the printed plan.
  - type: bool
  - default: off
  - context: user
- progressive_explain_costs: controls whether estimated startup and
total cost of each plan noded is added to the printed plan.
  - type: bool
  - default: true
  - context: user
    @rafaelthca
    rafaelthca authored and Commitfest Bot committed Apr 1, 2025
    Configuration menu
    Copy the full SHA
    8ca24cc View commit details
    Browse the repository at this point in the history

  2. [CF 5473] v15 - Proposal: Progressive explain 

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

https://commitfest.postgresql.org/patch/5473

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

Patch(es): https://www.postgresql.org/message-id/CAG0ozMrqMKcbcU1L9ON44himeEd=6qZ2_jH1fvF0yYD0zSgDYQ@mail.gmail.com
Author(s): Rafael Castro
    Commitfest Bot committed Apr 1, 2025
    Configuration menu
    Copy the full SHA
    377a142 View commit details
    Browse the repository at this point in the history
Loading