Re: Marking some contrib modules as trusted extensions - Mailing list pgsql-hackers

From Darafei "Komяpa" Praliaskouski
Subject Re: Marking some contrib modules as trusted extensions
Date
Msg-id CAC8Q8tKiedws=GNF_M50tV7qw7TJ0y_=+k+WJHPNc=VqScZr5A@mail.gmail.com
Whole thread Raw
In response to Marking some contrib modules as trusted extensions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Marking some contrib modules as trusted extensions  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Marking some contrib modules as trusted extensions  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
Hello,
 
btree_gin
btree_gist

I would even ask btree_gin and btree_gist to be moved to core.

btree_gist is shipping opclasses for built in types to be used in gist indexes. btree_* is confusing part in the name pretending there's some magic happening linking btree and gist.

gist is the most popular way to get geometric indexes, and these often need to be combined with some class identifier that's used in lookups together.
CREATE INDEX on geom_table using gist (zooom_level, geom); fails for no reason without btree_gist - types are shipped in core,
gist itself is not an extension, but letting to use one core mechanism with another in an obvious way is for some reason split out.


--
Darafei Praliaskouski

pgsql-hackers by date:

Previous
From: Soumyadeep Chakraborty
Date:
Subject: Re: Default JIT setting in V12
Next
From: Julien Rouhaud
Date:
Subject: Re: Collation versioning