| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Allow definition of lock mode for custom reloptions |
| Date: | 2019-09-25 01:22:06 |
| Message-ID: | E1iCw0M-0000YL-DD@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/69f94108079d70093b59096a3ae0ad82c842b4c0
Modified Files
--------------
contrib/bloom/blutils.c | 6 ++++--
src/backend/access/common/reloptions.c | 28 ++++++++++++----------------
src/include/access/reloptions.h | 11 +++++++----
3 files changed, 23 insertions(+), 22 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-09-25 03:12:31 | pgsql: Add dummy_index_am to src/test/modules/ |
| Previous Message | Michael Paquier | 2019-09-25 01:11:43 | pgsql: Fix failure with lock mode used for custom relation options |