Add object functions, modernize CI, and remove reg* pseudotypes#2
Add object functions, modernize CI, and remove reg* pseudotypes#2jnasbyupgrade wants to merge 33 commits into
Conversation
e9c24de Fix pg_regress on versions > 12 (Postgres-Extensions#5) c0af00f Improvements to HISTORY.asc 6e8f2a7 Allow use of sudo when installing an extension 705f1ec Don't run clean as part of make test 370fa8e Create test/sql during setup git-subtree-dir: pgxntool git-subtree-split: e9c24de986ddc85bbd1fb3149076888d075ce100
Use of those types is not supported by pg_upgrade
Also, add missing cat_tools requirement to META.in
Also, add missing cat_tools requirement to META.in
…nce into new_features
dbe7b50 to
40625c2
Compare
3b8cb2a Stamp 1.1.0 550a901 Remove commit.md (maintained in pgxntool-test) d73ca93 Add unique test database names to prevent conflicts (#13) 9b344be Add update-setup-files.sh for 3-way merging after pgxntool-sync (#12) ab7f6e2 Stamp 1.0.0 3a571ba Add pg_tle support and modernize test infrastructure (#11) b96ea6d Add support for Claude code; build and doc improvements (#9) git-subtree-dir: pgxntool git-subtree-split: 3b8cb2a96c2611bb44b1d69fd533fd0f23fa8995
Switching to pgxntool's new best practice of keeping versioned SQL files in git.
pg_identify_object_as_address() returns these as plain "table"/"index", and pg_get_object_address() doesn't recognize "partitioned table" or "partitioned index" at all, so the round-trip is broken.
pgxntool now assumes versioned files are checked in, so do that, but bump our version first. Also, add 0.1.0 from pgxn.
639756c Stamp 1.1.1 6ba3176 Fix pg_tle exception handler and empty upgrade files (#15) git-subtree-dir: pgxntool git-subtree-split: 639756c43a64717347b82b46acfec5be478a7bbf
new_features lacked the CI-monitoring instructions that already exist on master, so sessions working here didn't watch CI after pushes. Copy them over verbatim. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (40)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.