From f916512e4f8ad78f328c95c144b3fdde50b0667c Mon Sep 17 00:00:00 2001 From: Patrick Uiterwijk Date: Tue, 1 Nov 2016 22:17:28 +0000 Subject: [PATCH] By default, protect against schema changes in BDR Signed-off-by: Patrick Uiterwijk --- roles/postgresql_server_bdr/templates/postgresql.conf | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/roles/postgresql_server_bdr/templates/postgresql.conf b/roles/postgresql_server_bdr/templates/postgresql.conf index c997e51e1c..aea2ee8c8d 100644 --- a/roles/postgresql_server_bdr/templates/postgresql.conf +++ b/roles/postgresql_server_bdr/templates/postgresql.conf @@ -518,3 +518,9 @@ max_worker_processes = 100 # Useful options for playing with conflicts #bdr.default_apply_delay=2000 # milliseconds #bdr.log_conflicts_to_table=on + +# Do not allow getting a DDL lock without this option overridden on connect. +# This makes sure people read the documentation for BDR for schema changes before applying. +# http://bdr-project.org/docs/stable/ddl-replication.html +# Override by running: sudo -u postgres PGOPTIONS="-c bdr.permit_ddl_locking=on" psql koji +bdr.permit_ddl_locking=off