Thanks to visit codestin.com
Credit goes to github.com

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: postgres/postgres
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master@{1day}
Choose a base ref
...
head repository: postgres/postgres
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
  • 11 commits
  • 21 files changed
  • 7 contributors

Commits on Jun 26, 2025

  1. Expand virtual generated columns for ALTER COLUMN TYPE

    For the subcommand ALTER COLUMN TYPE of the ALTER TABLE command, the
    USING expression may reference virtual generated columns.  These
    columns must be expanded before the expression is fed through
    expression_planner and the expression-execution machinery.  Failing to
    do so can result in incorrect rewrite decisions, and can also lead to
    "ERROR:  unexpected virtual generated column reference".
    
    Reported-by: Alexander Lakhin <[email protected]>
    Reviewed-by: jian he <[email protected]>
    Discussion: https://postgr.es/m/[email protected]
    Richard Guo committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    5069fef View commit details
    Browse the repository at this point in the history
  2. doc: Fix indentation of MERGE synopsis.

    The convention in the documentation for other SQL commands is to
    indent continuation lines and sub-clauses in the "Synopsis" section by
    4 spaces, so do the same for MERGE.
    
    Author: Dean Rasheed <[email protected]>
    Reviewed-by: Nathan Bossart <[email protected]>
    Discussion: https://postgr.es/m/CAEZATCV+9tR9+WM-SCcdBEZ3x7WVxUpADD5jX9WeGX97z4LCGA@mail.gmail.com
    Backpatch-through: 15
    deanrasheed committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    eca624c View commit details
    Browse the repository at this point in the history
  3. doc: Updates for RETURNING OLD/NEW.

    Fix a couple of sentences in the documentation that were missed in
    commit 80feb72.
    
    Author: Dean Rasheed <[email protected]>
    Reviewed-by: Robert Treat <[email protected]>
    Discussion: https://postgr.es/m/CAEZATCUcqADJuapZSjPf2b6hFJ6AGOUwefRvh8Ht3UZoqqw69Q@mail.gmail.com
    deanrasheed committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    3ba9639 View commit details
    Browse the repository at this point in the history
  4. Make CREATE TABLE LIKE copy comments on NOT NULL constraints when req…

    …uested.
    
    Commit 14e87ff introduced support for adding comments to NOT NULL
    constraints. However, CREATE TABLE LIKE INCLUDING COMMENTS did not copy
    these comments to the new table. This was an oversight in that commit.
    
    This commit corrects the behavior by ensuring CREATE TABLE LIKE to also copy
    the comments on NOT NULL constraints when INCLUDING COMMENTS is specified.
    
    Author: Jian He <[email protected]>
    Co-authored-by: Álvaro Herrera <[email protected]>
    Reviewed-by: Fujii Masao <[email protected]>
    Discussion: https://postgr.es/m/[email protected]
    MasaoFujii and Álvaro Herrera committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    81ce602 View commit details
    Browse the repository at this point in the history
  5. pg_dump: include comments on valid not-null constraints, too

    We were missing collecting comments for not-null constraints that are
    dumped inline with the table definition (i.e., valid ones), because they
    aren't represented by a separately dumpable object.  Fix by creating
    separate TocEntries for the comments.
    
    Co-Authored-By: Jian He <[email protected]>
    Co-Authored-By: Álvaro Herrera <[email protected]>
    Reported-By: Fujii Masao <[email protected]>
    Reviewed-By: Fujii Masao <[email protected]>
    Discussion: https://postgr.es/m/[email protected]
    Álvaro Herrera and jianhe-fun committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    47fb875 View commit details
    Browse the repository at this point in the history
  6. docs: fix typo

    Álvaro Herrera committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    48c80ab View commit details
    Browse the repository at this point in the history
  7. Fix typo in comment

    Introduced by c2da1a5
    
    Reported-by: Michael Paquier <[email protected]>
    Discussion: https://postgr.es/m/[email protected]
    Álvaro Herrera committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    a3994ec View commit details
    Browse the repository at this point in the history
  8. Simplify vacuum VM update logging counters

    We can simplify the VM counters added in dc6acfd to
    lazy_vacuum_heap_page() and lazy_scan_new_or_empty().
    
    We won't invoke lazy_vacuum_heap_page() unless there are dead line
    pointers, so we know the page can't be all-visible.
    
    In lazy_scan_new_or_empty(), we only update the VM if the page-level
    hint PD_ALL_VISIBLE is clear, and the VM bit cannot be set if the page
    level bit is clear because a subsequent page update would fail to clear
    the visibility map bit.
    
    Simplify the logic for determining which log counters to increment based
    on this knowledge. Doing so is worthwhile because the old logic was
    confusing and misguided.
    
    Author: Melanie Plageman <[email protected]>
    Reviewed-by: Nazir Bilal Yavuz <[email protected]>
    Reviewed-by: Masahiko Sawada <[email protected]>
    Discussion: https://postgr.es/m/flat/CAAKRu_a9w_n2mwY%3DG4LjfWTvRTJtjbfvnYAKi4WjO8QXHHrA0g%40mail.gmail.com
    melanieplageman committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    060f420 View commit details
    Browse the repository at this point in the history
  9. Remove unused check in heap_xlog_insert()

    8e03eb9 reverted the commit 39b66a9 which allowed freezing
    in the heap_insert() code path but forgot to remove the corresponding
    check in heap_xlog_insert(). This code is extraneous but not harmful.
    However, cleaning it up makes it very clear that, as of now, we do not
    support any freezing of pages in the heap_insert() path.
    
    Author: Melanie Plageman <[email protected]>
    Reviewed-by: Tomas Vondra <[email protected]>
    Discussion: https://postgr.es/m/flat/CAAKRu_Zp4Pi-t51OFWm1YZ-cctDfBhHCMZ%3DEx6PKxv0o8y2GvA%40mail.gmail.com
    Backpatch-through: 14
    melanieplageman committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    483f724 View commit details
    Browse the repository at this point in the history
  10. Correct misleading error messages

    Commit 7d6d2c4 dropped opcintype from the index AM strategy
    translation API.  But some error messages about failed lookups still
    mentioned it, even though it was not used for the lookup.  Fix by
    removing ipcintype from the error messages as well.
    petere committed Jun 26, 2025
    Configuration menu
    Copy the full SHA
    95e12d4 View commit details
    Browse the repository at this point in the history
  11. Configuration menu
    Copy the full SHA
    7fb3c38 View commit details
    Browse the repository at this point in the history
Loading