-- what happens if we specify slightly misformatted abstime?
INSERT INTO ABSTIME_TBL (f1) VALUES ('Feb 35, 1946 10:00:00');
psql:/data/gpadmin/pulse2-agent/agents/agent1/work/GPDB-43_STABLE-TINC-kerberos_smoke/rhel6_kerberos_smoke/cdbunit/tinc/tincrepo/mpp/gpdb/tests/security/kerberos/output/abstime_orca.sql:38: ERROR: date/time field value out of range: "Feb 35, 1946 10:00:00"
LINE 1: INSERT INTO ABSTIME_TBL (f1) VALUES ('Feb 35, 1946 10:00:00'...
^
HINT: Perhaps you need a different "datestyle" setting.
INSERT INTO ABSTIME_TBL (f1) VALUES ('Feb 28, 1984 25:08:10');
psql:/data/gpadmin/pulse2-agent/agents/agent1/work/GPDB-43_STABLE-TINC-kerberos_smoke/rhel6_kerberos_smoke/cdbunit/tinc/tincrepo/mpp/gpdb/tests/security/kerberos/output/abstime_orca.sql:39: ERROR: date/time field value out of range: "Feb 28, 1984 25:08:10"
LINE 1: INSERT INTO ABSTIME_TBL (f1) VALUES ('Feb 28, 1984 25:08:10'...
^
-- badly formatted abstimes: these should result in invalid abstimes
INSERT INTO ABSTIME_TBL (f1) VALUES ('bad date format');
psql:/data/gpadmin/pulse2-agent/agents/agent1/work/GPDB-43_STABLE-TINC-kerberos_smoke/rhel6_kerberos_smoke/cdbunit/tinc/tincrepo/mpp/gpdb/tests/security/kerberos/output/abstime_orca.sql:42: ERROR: invalid input syntax for type abstime: "bad date format"
LINE 1: INSERT INTO ABSTIME_TBL (f1) VALUES ('bad date format');
^
INSERT INTO ABSTIME_TBL (f1) VALUES ('Jun 10, 1843');
psql:/data/gpadmin/pulse2-agent/agents/agent1/work/GPDB-43_STABLE-TINC-kerberos_smoke/rhel6_kerberos_smoke/cdbunit/tinc/tincrepo/mpp/gpdb/tests/security/kerberos/output/abstime_orca.sql:43: ERROR: cannot convert abstime "invalid" to timestamp
psql:/path/sql_file:1: WARNING: The distributed transaction 'Abort Prepared' broadcast failed to one or more segments for gid = 1426021631-0000003259.
psql:/path/sql_file:1: NOTICE: Releasing segworker groups to retry broadcast.
psql:/path/sql_file:1: NOTICE: Retry of the distributed transaction 'Abort Prepared' broadcast succeeded to the segments for gid = 1426021631-0000003259.
psql:/path/sql_file:1: ERROR: Raise an error as directed by Debug_abort_after_distributed_prepared (xact.c:3464)
psql:/path/sql_file:1: ERROR: Raise an error as directed by Debug_abort_after_distributed_prepared
SELECT * FROM distxact1_4;
a
---
...
...
@@ -229,7 +231,7 @@ SET
CREATE TABLE distxact2_1 (a int);
psql:/path/sql_file:1: NOTICE: Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Greenplum Database data distribution key for this table.
HINT: The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
psql:/path/sql_file:1: NOTICE: Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Greenplum Database data distribution key for this table.
HINT: The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
SET debug_abort_after_distributed_prepared = true;
SET
COMMIT;
psql:/path/sql_file:1: ERROR: Raise an error as directed by Debug_abort_after_distributed_prepared (xact.c:3484)
psql:/path/sql_file:1: ERROR: Raise an error as directed by Debug_abort_after_distributed_prepared
RESET debug_abort_after_distributed_prepared;
RESET
SELECT * FROM distxact1_1;
...
...
@@ -93,7 +93,7 @@ SET
SET debug_dtm_action_protocol = "prepare";
SET
COMMIT;
psql:/path/sql_file:1: ERROR: The distributed transaction 'Prepare' broadcast failed to one or more segments for gid = 1426046326-0000016107. (cdbtm.c:689)
psql:/path/sql_file:1: ERROR: The distributed transaction 'Prepare' broadcast failed to one or more segments for gid = 1485397982-0000000407. (cdbtm.c:689)
RESET debug_dtm_action;
RESET
RESET debug_dtm_action_target;
...
...
@@ -205,7 +205,7 @@ COMMIT;
psql:/path/sql_file:1: WARNING: The distributed transaction 'Abort Prepared' broadcast failed to one or more segments for gid = 1426046326-0000016121.
psql:/path/sql_file:1: NOTICE: Releasing segworker groups to retry broadcast.
psql:/path/sql_file:1: NOTICE: Retry of the distributed transaction 'Abort Prepared' broadcast succeeded to the segments for gid = 1426046326-0000016121.
psql:/path/sql_file:1: ERROR: Raise an error as directed by Debug_abort_after_distributed_prepared (xact.c:3484)
psql:/path/sql_file:1: ERROR: Raise an error as directed by Debug_abort_after_distributed_prepared
SELECT * FROM distxact1_4;
psql:/path/sql_file:1: WARNING: One or more columns in the following table(s) do not have statistics. (see log for column name(s))
psql:/path/sql_file:1: NOTICE: Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Greenplum Database data distribution key for this table.
HINT: The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
psql:/path/sql_file:1: NOTICE: Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Greenplum Database data distribution key for this table.
HINT: The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.