Fixes message errors

pull/7240/head
gindibay 2023-11-08 06:56:21 +03:00
parent ba377ecaab
commit 5f8f1d312d
2 changed files with 7 additions and 7 deletions

View File

@ -28,7 +28,7 @@ SELECT citus.mitmproxy('conn.onQuery(query="CREATE").kill()');
CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1); CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1);
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: connection to the remote node localhost:xxxxx failed with the following error: connection not open ERROR: connection to the remote node localhost:xxxxx failed with the following error: connection not open
SELECT citus.mitmproxy('conn.allow()'); SELECT citus.mitmproxy('conn.allow()');
mitmproxy mitmproxy
@ -62,7 +62,7 @@ SELECT citus.mitmproxy('conn.onQuery(query="CREATE").kill()');
CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1); CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1);
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: connection to the remote node localhost:xxxxx failed with the following error: connection not open ERROR: connection to the remote node localhost:xxxxx failed with the following error: connection not open
SELECT citus.mitmproxy('conn.allow()'); SELECT citus.mitmproxy('conn.allow()');
mitmproxy mitmproxy
@ -90,7 +90,7 @@ SELECT citus.mitmproxy('conn.onQuery(query="CREATE").cancel(' || pg_backend_pid(
CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1); CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1);
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: canceling statement due to user request ERROR: canceling statement due to user request
SELECT citus.mitmproxy('conn.allow()'); SELECT citus.mitmproxy('conn.allow()');
mitmproxy mitmproxy
@ -116,7 +116,7 @@ SELECT citus.mitmproxy('conn.onQuery(query="CREATE").cancel(' || pg_backend_pid(
CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1); CREATE INDEX CONCURRENTLY idx_index_test ON index_test(id, value_1);
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: canceling statement due to user request ERROR: canceling statement due to user request
SELECT citus.mitmproxy('conn.allow()'); SELECT citus.mitmproxy('conn.allow()');
mitmproxy mitmproxy
@ -143,7 +143,7 @@ SELECT citus.mitmproxy('conn.onQuery(query="DROP INDEX CONCURRENTLY").kill()');
DROP INDEX CONCURRENTLY IF EXISTS idx_index_test; DROP INDEX CONCURRENTLY IF EXISTS idx_index_test;
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: connection to the remote node localhost:xxxxx failed with the following error: connection not open ERROR: connection to the remote node localhost:xxxxx failed with the following error: connection not open
SELECT citus.mitmproxy('conn.allow()'); SELECT citus.mitmproxy('conn.allow()');
mitmproxy mitmproxy
@ -171,7 +171,7 @@ INSERT INTO index_test_2 VALUES (1, 1), (1, 2);
CREATE UNIQUE INDEX CONCURRENTLY index_test_2_a_idx ON index_test_2(a); CREATE UNIQUE INDEX CONCURRENTLY index_test_2_a_idx ON index_test_2(a);
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: could not create unique index "index_test_2_a_idx_1880019" ERROR: could not create unique index "index_test_2_a_idx_1880019"
DETAIL: Key (a)=(1) is duplicated. DETAIL: Key (a)=(1) is duplicated.
CONTEXT: while executing command on localhost:xxxxx CONTEXT: while executing command on localhost:xxxxx

View File

@ -90,7 +90,7 @@ SELECT create_distributed_table('failover_to_local', 'a', shard_count=>32);
CREATE INDEX CONCURRENTLY ON failover_to_local(a); CREATE INDEX CONCURRENTLY ON failover_to_local(a);
WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state. WARNING: Commands that are not transaction-safe may result in partial failure, potentially leading to an inconsistent state.
If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object, If the problematic command is a CREATE operation, consider using the 'IF EXISTS' syntax to drop the object,
if applicable, and then reattempt the original command. if applicable, and then re-attempt the original command.
ERROR: the total number of connections on the server is more than max_connections(100) ERROR: the total number of connections on the server is more than max_connections(100)
HINT: Consider using a higher value for max_connections HINT: Consider using a higher value for max_connections
-- reset global GUC changes -- reset global GUC changes