Some time zones that the host operating system supports are not supported bythe Greenplum Database. For example, if the OS time zone is "Asia/Jakarta," the corresponding time zone abbreviation "WIT" is not supported in the Greenplum Database. gpstop gpadmin=# show timezone; gpadmin=# select * from pg_timezone_names where name='Asia/Jakarta'; gpadmin=# create table t1(id timestamp with time zone); gpadmin=# insert into t1 values('2011-11-23 10:33:48.888539 WIT'); Root Cause: If Greenplum is using an unsupported time zone such as "Asia/Jakarta" and its abbreviation "WIT," any Greenplum internal operation that inserts into gp_configuration_history triggers errors since gp_configuration_history has a column "time" with type"timestamp with time zone." For example, gprecoverseg may be affected because it will modify gp_segment_configuration and also gp_configuration_history. The modification of the two tables is in the same transaction so if the operation on gp_configuration_history fails, the whole transaction will fail and rollback. As a result, the Greenplum configuration will in an unhealthy status. Fix Follow these steps:
Example: gpstop -r gpadmin=# select * from pg_timezone_abbrevs where abbrev='WIT'; gpadmin=# insert into t1 values('2011-11-23 10:33:48.888539 WIT'); |