citus

Commit Graph

Author	SHA1	Message	Date
Nils Dijk	97da44558b	Description: Fix failures of tests on recent postgres builds In recent postgres builds you cannot set client_min_messages to values higher then ERROR, if will silently set it to ERROR if so. During some tests we would set it to fatal to hide random values (eg. pid's of processes) from the test output. This patch will use different tactics for hiding these values.	2018-11-13 16:53:05 +01:00
Onder Kalaci	85d7d074c3	Add cancellation tests for multi shard modification queries	2018-10-26 15:07:52 +03:00
Jason Petersen	ee4114bc7a	Failure tests for modifying multiple shards in txn Tests various failure points during a multi-shard modification within a transaction with multiple statements. Verifies three cases: * Reference tables (single shard, many placements) * Normal table with replication factor two * Multi-shard table with no replication In the replication-factor case, we expect shard health to be affected in some transactions; most others fail the transaction entirely and all we need verify is that no effects of the transaction are visible. Had trouble testing the final PREPARE/COMMIT/ROLLBACK phase of the 2pc, in particular because the error message produced includes the PID of the backend, which is unpredictable.	2018-10-09 09:17:32 -06:00

Author

SHA1

Message

Date

Nils Dijk

97da44558b

Description: Fix failures of tests on recent postgres builds

In recent postgres builds you cannot set client_min_messages to
values higher then ERROR, if will silently set it to ERROR if so.

During some tests we would set it to fatal to hide random values
(eg. pid's of processes) from the test output. This patch will use
different tactics for hiding these values.

2018-11-13 16:53:05 +01:00

Onder Kalaci

85d7d074c3

Add cancellation tests for multi shard modification queries

2018-10-26 15:07:52 +03:00

Jason Petersen

ee4114bc7a

Failure tests for modifying multiple shards in txn

Tests various failure points during a multi-shard modification within
a transaction with multiple statements. Verifies three cases:

  * Reference tables (single shard, many placements)
  * Normal table with replication factor two
  * Multi-shard table with no replication

In the replication-factor case, we expect shard health to be affected
in some transactions; most others fail the transaction entirely and
all we need verify is that no effects of the transaction are visible.

Had trouble testing the final PREPARE/COMMIT/ROLLBACK phase of the 2pc,
in particular because the error message produced includes the PID of
the backend, which is unpredictable.

2018-10-09 09:17:32 -06:00

3 Commits (1656b519c49062dee5bb5fc8174963821dda9f17)