Vacuum now uses distributed lowest dxid to decide oldest transaction *globally*
running in cluster to make sure tuple is DEAD globally before removing the
same. HeapTupleSatisfiesVacuum() consults distributed snapshot by reverse
mapping localXid to distributed xid to check xminAllDistributedSnapshots and
verifies its not needed anymore globally. Note the check is conservative from
perpective if cannot check against distributed snapshot (like utility mode
vacuum) will try to keep the tuple than prematurely getting rid of it and
suffering the same problem.

This fixes the problem of not removing the tuple still needed. Earlier it
performed the check just based on local information (oldestXmin) on a segment,
and hence may cleanup a tuple visible to a distributed query yet to reach the
segment, which breaks snapshot isolation.

Fixes #801.

For vacuum, page pruning and freezing to perform its job correctly on QE's, it
needs to know globally what's the lowest dxid till any transaction can see in
full cluster. Hence QD must calculate and send that info to QE. For this purpose
using logic similar to one for calculating globalxmin by local snapshot. TMGXACT
for global transactions serves similar to PROC and hence its leveraged to
provide us lowest gxid for its snapshot. Further using its array, shmGxactArray,
can easily find the lowest across all global snapshots and pass down to QE via
snapshot.

Adding unit test for createDtxSnapshot along with the change.

- now correctly finds header
  - used `getversion` to generate file name
  - Using `getversion --short` for GPDB version string

Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NJingyi Mei <jmei@pivotal.io>

We no longer support FTS fault strategies other then filerep and
none, so abort upgrades in case any other fault strategy is set
in the old cluster.

Only SAN and FILEREPLICATION strategies have been supported for
quite some time, remove the old deprecated definitions.

The SAN FTS failover strategy is deprecated and no longer maintained,
as it's no longer needed. Retire the dead code to clean up. Since we
currently are in catalog freeze, the gp_san_configuration catalog is
left in place but will be removed once we open up for the next major
version cycle. Since the gp_san_config header file contains catalogs
for general FTS fault strategies, rename the file for clarity.

* moving linux kerberos client instructions to dedicated topic, and placing it parallel with existing windows topic

* removing map and dita files for connectivity package, which is no longer provided

* removing more references to connectivity packages; conditionalizing postgres odbc/jdbc vs datadirect drivers for oss/pivotal audiences

* adding .ditaval for handling pivotal conditions; [ci skip]

* relocating pivotal ditaval

Commit ca028ee8 reformatted queries to capitalize keywords, accidentally
capitalizing a "%s" into a "%S".  This commit fixes that.
the quoting of the cast to fix the syntax error.

This test is to validate bitmap works fine even if complex bitmap and /
or logic on the inner side of nested loop.

These are the changes required to accommodate ORCA changes from PR:
https://github.com/greenplum-db/gporca/pull/159

Bumps up ORCA version to v2.29.0
Signed-off-by: NJemish Patel <jpatel@pivotal.io>

Commit ca028ee8 reformatted the queries to capitalize keywords. Remove
the quoting of the cast to fix the syntax error.

- Before this change, if you were iterating in a container and wanted to
  run the compilation again, you would have to remove gpaddon because
  its presence caused the `cp` to fail
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NMelanie Plageman <mplageman@pivotal.io>

Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NMelanie Plageman <mplageman@pivotal.io>

Modify previous behave tests to address test flakiness
-- Use gpstop instead of pkill
-- Reduce min_query_time to 0
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NMelanie Plageman <mplageman@pivotal.io>

Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Bump orca version to 2.28.0
Signed-off-by: NJemish Patel <jpatel@pivotal.io>

Signed-off-by: NMelanie Plageman <mplageman@pivotal.io>

- This was missed in commit aaa88b21

When creating HHashTable, instead of using the available memory as the
sole basis to determine the number of buckets, it now computes nbuckets
as a function of estimated groups/entries given by the planner. To
prevent performance degradation when the statistics are off, the
hash table expands by doubling the number of buckets and rehashing all
the entries until it is out of memory.
If more space is needed, HHashTable spills to disk as before, but it can
now accurately allocate buckets when the spill files are reloaded based
on the number of entries spilled.

This commit also makes other minor fixes:
  - Change calcHashAggTableSizes() signature to make it reusable
  - Keep track of in-memory entries in the HT
  - Add tests for when it overflows multiple times
  - Estimate the overhead per entry in the hash table more acurately
  - Refactor statistics collection for EXPLAIN ANALZYE

[ci skip]

[ci skip]

* add idle time to session_level_memory_consumption view

* add idle time to table intro

* GPDB DOCS - update pl/java topic - remove embedded Java runtime info

[ci skip]

* update link.
[ci skip]

- This also fixes a bug where we looked for the report file in the
  wrong directory
Signed-off-by: NKaren Huddleston <khuddleston@pivotal.io>

Commit fb93e7e7 removed this field, but commit 9a817d45 accidentally
resurrected it. Remove it again.

`build_exclude_list()` will return a statically allocated empty string if the
number of exlude arguments is zero. We should check for this in the caller
before freeing the pointer returned by it.

Signed-off-by: NTom Meyer <tmeyer@pivotal.io>