Files
Vinod Sridharan 14b27c08e9 Merged PR 1817813: [ExtendedRum] Move pg_documentdb_extended_rum to the top level folder
### Does this PR have any customer impact?
Yes

### Type (Feature, Refactoring, Bugfix, DevOps, Testing, Perf, etc)
Feature

### Does it involve schema level changes? (Table, Column, Index, UDF, etc level changes)
No

### Are you introducing any new config? If yes, do you have tests with and without them being set?
No

### ChangeLog (Refer [Template](../oss/CHANGELOG.md))

### Description
Move pg_documentdb_extended_rum to the top level folder from the internal folder since documentdb (tests and product) now has a dependency on it.

pg_documentdb_extended_rum is a fork of  the RUM Extension that provides extensions that were needed for documentdb. This includes the ability to push down order by and group by to the index; The ability to do index only scans; improvements on vacuum and handling of page splits; index scan improvements while retaining the original inverted index for text search capabilities that the RUM index had.

Signed-off-by: Shuai Tian <shuaitian@microsoft.com>
2025-09-29 22:38:08 -07:00
..

DocumentDB RUM - RUM access method

Introduction

The rum module provides an access method to work with a RUM index. It is based on the GIN access method's code.

documentdb_rum is a fork of the RUM access method that extends it to allow more scenarios centered around documents. Note that the folloiwng invariants are true:

  1. From a storage standpoint, it has the same layout and content on disk as RUM (it is fully back-wards compatible)
  2. All changes must be made only on the query path and volatile path or in a way that works for indexes that are built with the default RUM repo.

License

This module is available under the license similar to PostgreSQL.

Installation

run make install on this directory after pulling in the rest of documentdb.

Authors

See README