Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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/5105~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/5105
Choose a head ref
  • 2 commits
  • 1 file changed
  • 2 contributors

Commits on Mar 30, 2025

  1. Prevent misleading entries in pg_stat_activity.

    In some cases, such as handling "Describe" messages, cleaning up
    temporary relations at exit, or managing client read interrupts,
    backends can remain in an "idle" state but still set xact_start
    in pg_stat_activity. This results in misleading entries where
    "idle" backends appear to have non-NULL transaction times.
    Additionally, during temp relation cleanup or interrupt handling,
    xact_start might incorrectly reflect the timestamp of
    the last executed query, further confusing users.
    
    This commit addresses the issue by ensuring pg_stat_activity
    does not show transaction and query start times for "idle" backends,
    setting them to NULL instead. This prevents confusing entries
    for "idle" backends.
    
    While it would be possible to correctly track backend states and
    set timestamps, this approach would introduce performance overhead
    due to frequent updates of state and timestamp. Moreover, it is not
    particularly beneficial to treat processes like "Describe" message handling,
    temp relation cleanup, or client read interrupts as regular transactions.
    Therefore, the simpler and more efficient solution was adopted.
    
    Discussion: https://postgr.es/m/20140424101827.2714.39486@wrigleys.postgresql.org
    MasaoFujii authored and Commitfest Bot committed Mar 30, 2025
    Configuration menu
    Copy the full SHA
    590f0a8 View commit details
    Browse the repository at this point in the history
  2. [CF 5105] v2 - Prevent incorrect entries in pg_stat_activity.

    This branch was automatically generated by a robot using patches from an
    email thread registered at:
    
    https://commitfest.postgresql.org/patch/5105
    
    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/b5c6f74d-302a-41a9-8b9f-7b5ceb230d4a@oss.nttdata.com
    Author(s): Fujii Masao
    Commitfest Bot committed Mar 30, 2025
    Configuration menu
    Copy the full SHA
    ee928d1 View commit details
    Browse the repository at this point in the history
Loading