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/5720~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/5720
Choose a head ref
  • 2 commits
  • 10 files changed
  • 2 contributors

Commits on Apr 29, 2025

  1. virtual generated column as partition key

    demo:
    CREATE TABLE t(f1 bigint, f2 bigint GENERATED ALWAYS AS (f1 * 2) VIRTUAL) PARTITION BY RANGE (f2);
    but partition key can not be expression on top of virtual generated column.
    so the following is not allowed:
    CREATE TABLE t(f1 bigint, f2 bigint GENERATED ALWAYS AS (f1 * 2) VIRTUAL) PARTITION BY RANGE ((f2+1));
    
    The virtual generated column expression for each partition must match with
    the partitioned table, since it is used as a partition key. Otherwise, the
    partition bound would be dynamically evaluated.
    
    cross partition update tests added.
    
    A virtual generated column entry in the pg_partitioned_table catalog is marked
    as non-zero partattrs and a non-null partexprs, which is abnormal. Normally,
    either partattrs is non-zero or partexprs is null.
    we should mention this in the doc/src/sgml/catalogs.sgml
    
    discussion: https://postgr.es/m/
    jianhe-fun authored and Commitfest Bot committed Apr 29, 2025
    Configuration menu
    Copy the full SHA
    674a6fb View commit details
    Browse the repository at this point in the history
  2. [CF 5720] v1 - virtual generated column as partition key

    This branch was automatically generated by a robot using patches from an
    email thread registered at:
    
    https://commitfest.postgresql.org/patch/5720
    
    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/CACJufxF9RV2_iHBAG0AfCyt5c-1zJkh_Jc7F1tZfk3m3N+E=qA@mail.gmail.com
    Author(s): Jian He
    Commitfest Bot committed Apr 29, 2025
    Configuration menu
    Copy the full SHA
    59610e5 View commit details
    Browse the repository at this point in the history
Loading