Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #5059
Updated
CREATE INDEX
to support operator classes e.gjsonb_path_ops
, storage parameters e.ggin_pending_list_limit
and index methods forBRIN
,BTREE
,GIN
,GIST
,HASH
Added integration tests for index methods and storage parameters
There are many op classes and it may not be possible to validate them, extra ones are added by extensions, and the data types they support
The optional WITH clause specifies storage parameters for the index. Each index method has its own set of allowed storage parameters. https://www.postgresql.org/docs/16/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
Index storage parameters are possible to validate, along with the arguments
e.g
Added
CreateIndexMixin
to annotate errors with storage parametersUpdated fixtures with different index methods and invalid options
📔
ALTER INDEX
is not currently implemented in any grammar as is non-standard (as sqlite doesn't supportALTER INDEX
)Currently
DROP INDEX
must be used instead