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

Commits on May 31, 2025

  1. Allow table AMs to define their own reloptions

    With the help of the new routine 'relation_options', table access
    methods can now define their own reloptions.
    
    These options can be set via the following commands:
    1. CREATE TABLE ... USING table_am
           WITH (option1='value1', option2='value2');
    2. ALTER TABLE ...
           SET (option1 'value1', option2 'value2');
    3. ALTER TABLE ... SET ACCESS METHOD table_am
           OPTIONS (option1 'value1', option2 'value2');
    
    When changing table's access method, the settings from the former
    table AM can be dropped (if not supported by the new table AM) via:
    DROP option, or, updated via: SET option 'value'.
    
    Before this commit, tables using different table AMs than heap were
    able to use heap's reloptions (fillfactor, toast_tuple_target,
    etc...). Now, this is not the case anymore: if the table AM needs
    to have access to settings similar to heap ones, they must
    explicitly define them.
    
    This work is directly derived from SadhuPrasad's patch named:
    v4-0001-PATCH-V4-Per-table-storage-parameters-for-TableAM.patch
    Julien Tachoires authored and Commitfest Bot committed May 31, 2025
    Configuration menu
    Copy the full SHA
    6d1d8c0 View commit details
    Browse the repository at this point in the history
  2. Add the "dummy_table_am" test module

    This test module is in charge of testing table AM reloptions. It's
    very similar to what we do in dummy_index_am as we have to exercise
    the exact same kind of feature.
    Julien Tachoires authored and Commitfest Bot committed May 31, 2025
    Configuration menu
    Copy the full SHA
    82ac4c4 View commit details
    Browse the repository at this point in the history
  3. [CF 5631] v4 - Allow table AMs to define their own reloptions

    This branch was automatically generated by a robot using patches from an
    email thread registered at:
    
    https://commitfest.postgresql.org/patch/5631
    
    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/20250526110619.oepaf5dbzq3hjuij@poseidon.home.virt
    Author(s): Julien Tachoires
    Commitfest Bot committed May 31, 2025
    Configuration menu
    Copy the full SHA
    36c5ab5 View commit details
    Browse the repository at this point in the history
Loading