postgresql/contrib/bloom
Michael Paquier 69f9410807 Allow definition of lock mode for custom reloptions
Relation options can define a lock mode other than AccessExclusiveMode
since 47167b7, but modules defining custom relation options did not
really have a way to enforce that.  Correct that by extending the
current API set so as modules can define a custom lock mode.

Author: Michael Paquier
Reviewed-by: Kuntal Ghosh
Discussion: https://postgr.es/m/20190920013831.GD1844@paquier.xyz
2019-09-25 10:13:52 +09:00
..
expected Fix failure with lock mode used for custom relation options 2019-09-25 10:07:23 +09:00
sql Fix failure with lock mode used for custom relation options 2019-09-25 10:07:23 +09:00
t Don't fall off the end of perl functions 2018-05-27 09:08:42 -04:00
.gitignore Bloom index contrib module 2016-04-01 16:42:24 +03:00
Makefile Add PGXS options to control TAP and isolation tests, take two 2018-12-03 09:27:35 +09:00
blcost.c Refactor index cost estimation functions in view of IndexClause changes. 2019-02-15 13:05:19 -05:00
blinsert.c Report progress of CREATE INDEX operations 2019-04-02 15:18:08 -03:00
bloom--1.0.sql Minor fixes in contrib installation scripts. 2016-06-14 10:47:06 -04:00
bloom.control Bloom index contrib module 2016-04-01 16:42:24 +03:00
bloom.h Phase 2 pgindent run for v12. 2019-05-22 13:04:48 -04:00
blscan.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
blutils.c Allow definition of lock mode for custom reloptions 2019-09-25 10:13:52 +09:00
blvacuum.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
blvalidate.c Update copyright for 2019 2019-01-02 12:44:25 -05:00