6 Commits (7e3f2486f30597a724988a15f46daa0ea8cc1966)

Author	SHA1	Message	Date
Burak Velioglu	7e3f2486f3	Remove metadata by checking isactive	2022-01-03 17:55:26 +03:00
Halil Ozan Akgul	4c8f79d7dd	Turn metadata sync on in failure schedule	2021-12-08 11:22:56 +03:00
Onder Kalaci	2c349e6dfd	Use current user to sync metadata ... Before this commit, we always synced the metadata with superuser. However, that creates various edge cases such as visibility errors or self distributed deadlocks or complicates user access checks. Instead, with this commit, we use the current user to sync the metadata. Note that, `start_metadata_sync_to_node` still requires super user because accessing certain metadata (like pg_dist_node) always require superuser (e.g., the current user should be a superuser). However, metadata syncing operations regarding the distributed tables can now be done with regular users, as long as the user is the owner of the table. A table owner can still insert non-sense metadata, however it'd only affect its own table. So, we cannot do anything about that.	2021-07-16 13:25:27 +02:00
Ahmet Gedemenli	ed3b98a80b	Add failure test for stop_metadata_sync_to_node (#5102)	2021-07-08 18:23:19 +03:00
Hanefi Onaldi	878513f325	Remove all occurences of replication_model GUC	2021-05-21 16:14:59 +03:00
Hanefi Onaldi	4dd1f5784b	Failure&cancellation tests for mx metadata sync ... Failure&Cancellation tests for initial start_metadata_sync() calls to worker and DDL queries that send metadata syncing messages to an MX node Also adds message type definitions for messages that are exchanged during metadata syncing -	2019-02-01 11:50:25 +03:00