Skip to content

Fix version upgrade and downgrade above 0.1.4#11

Draft
mrimbault wants to merge 1 commit intoadjust:masterfrom
mrimbault:fix_parallel_compat_upgrade_path_pg_10
Draft

Fix version upgrade and downgrade above 0.1.4#11
mrimbault wants to merge 1 commit intoadjust:masterfrom
mrimbault:fix_parallel_compat_upgrade_path_pg_10

Conversation

@mrimbault
Copy link
Copy Markdown

@mrimbault mrimbault commented Mar 19, 2026

  • remove the previously introduced direct upgrade path from 0.1.4 to
    0.1.6
  • change the upgrade and downgrade path 0.1.4 <-> 0.1.5:
    • only use CREATE OR REPLACE AGGREGATE
    • drop support for PG 11- that doesn't support it
  • keep upgrade and downgrade path 0.1.5 <-> 0.1.6 as a no-op

Reasoning:

  • the parallel safety addition introduced by 0.1.5 is only marginally
    useful for this extension functions, since the main use case requires
    using ordered aggregates
  • safely redefining aggregates that may have dependent objects without
    DROP requires CREATE OR REPLACE AGGREGATE, introduced in PostgreSQL 12
  • supporting an alternative logic for PG 11- versions would require
    extra logic, while these versions have already been EOL for several
    years

@mrimbault mrimbault self-assigned this Mar 19, 2026
- remove the previously introduced direct upgrade path from 0.1.4 to
  0.1.6
- change the upgrade and downgrade path 0.1.4 <-> 0.1.5:
  - only use CREATE OR REPLACE AGGREGATE
  - drop support for PG 11- that doesn't support it
- keep upgrade and downgrade path 0.1.5 <-> 0.1.6 as a no-op

Reasoning:
- the parallel safety addition introduced by 0.1.5 is only marginally
  useful for this extension functions, since the main use case requires
  using ordered aggregates
- safely redefining aggregates that may have dependent objects without
  DROP requires CREATE OR REPLACE AGGREGATE, introduced in PostgreSQL 12
- supporting an alternative logic for PG 11- versions would require
  extra logic, while these versions have already been EOL for several
  years
@mrimbault mrimbault force-pushed the fix_parallel_compat_upgrade_path_pg_10 branch from 1487ac0 to 0c6142e Compare March 19, 2026 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant