Tags: shardman.

...rgeAppend, a SubqueryScan nodes.
Tags: shardman.

Tags: shardman.

Replace find_ok assert with elog panic message.

Improve the elog panic message introduced in previous commit.
Fix ForeignScan estimation logic.

Switch from AQO_EXPLAIN define to the two user GUCS: aqo.details
and aqo.show_hash.
New ExplainOneNode hook allows to add info into explain of each node.

AQO supports push-down of trivial JOIN and JOIN with mergejoinable clauses.

short-living planner memory context.
Some indentations fixed.

Big commit. To avoiding UPDATE/UPDATE/DELETE/INSERT conflicts we
use user locks on a pair (query_hash, fspace_hash) to guarantee that
only one backend can do INSERT/UPDATE/DELETE of a aqo table row.
Also we use dirty snapshot to see concurrently inserted/updated tuples.
Such conflict may cause deadlocks on end-of-transaction waiting.
Currently, if we detected such conflict, we refuse from we ML-base
changing.

collection.
Add some comments on auto tuning algorithm.
change the intelligent.sql test to avoid unsteady behaviour in the
intelligent mode.
Change the logic of a node hash showing.
Add regression test on forced stat collection mode.

Enable ICU and TAP tests in the AQO CI

Add regression test on currently unsupported planner clauses.

...f sorting table rows use md5(string) instead of string itself.
Tags: aqo.

... path.parent->subroot as the planning context for interpretation of the subpath.
Tags: aqo.

...ning mode without using AQO. In this mode we aren't going to use any such data during a statistics gathering at the end of execution. Also add more safe initialization of a predicted cardinality field. Tags: aqo.

...and remove comment. Induced by a test passing problem on the powerpc node of the buildfarm.
Tags: aqo.

...LAIN ANALYZE of a join node.
Tags: aqo.

...ort observation of a contrib-check in browser (By A.Lakhin report).
Tags: aqo.

smoother applying.

test for successful passing.
Check on passing of this rule is added into CI/CD script.
Further we need to implement execution of the regression tests in
different modes of AQO repeatedly on the same instance and the same database.

parallel operation, as either the master or a worker.

Now AQO could clean global data, such of query_text at the end
of transaction. It is needed because errors during query execution
phases. We need to be sure that all such data cleaned before the next
query execution.
Interface of the add_query_text routine changed.

the query must be read-only (by the flag XactReadOnly).

Add ignore option in pg_regress schedule for non-passed tests.

It is needed to exclude problems with recursive execution induced
by cache invalidation.

established by previous execution of this plan in another query.