Gpcrondump and gpdbrestore redirect stderr into status file for segments,
errors should be reflected into the master's report file.
Warnings will be given if process completed but errors were generated in
the report file.

Also made some refactor of the code.

This commit also reverts 08f4ada7.

Authors: Pengcheng Tang, Nikhil Kak

Gpcrondump and gpdbrestore redirect stderr into status file for segments,
errors should be reflected into the master's report file.
Warnings will be given if process completed but errors were generated in
the report file.

Also made some refactor of the code.

Authors: Pengcheng Tang, Nikhil Kak

This patch replaces all occurrences of pgsql-bugs@postgresql.org with
bugs@greenplum.org. Pointers to the pgsql-bugs mailinglist in the code
remain as they re. Regression and BugBuster tests are also patched.

When the segment dump process crashes, master ends up waiting
infinitely. So adding a fault detection mechanism to periodically
check if the segment dump process is alive.

Fix DDBoost restore to retrieve dump file from Data Domain Server;

DDBoost restore incorrectly assumes that the post schema dump file is
located locally, and failed the restore process.

Gpcrondump now sets the correct schema for schema altered sub partition tables;

If sub partition tables got altered and set to different schema,
gpcrondump incorrectly sets the schema for these modified tables.

Fix the usage of fmtId() to correctly consume the returned value;

fmtId() reuses the same buffer; so before calling fmtId() for the 2nd time,
consume the value in the returned buffer.

Fix restore failure when exchange partition with external tables has 'LOG ERRORS' statement.

If an external table has a "LOG ERRORS" statement in the definition, it explicitly
creates the error table. Hence, restore fails due to name conflicts with the subpartition table name.

Authors : Pengcheng Tang, Nikhil Kak, Isobel Redelmeier