Select on table produces "could not write block 0 of base/xxxxx/t_xxxxx" message

Products

• VMware Tanzu Greenplum

Issue/Introduction

Customer encounters errors similar to the ones below on select statements. Selects on different tables cause write errors in unrelated tables below (t_16413137 does not relate to the table being selected on):

select count(1) from public.table7d
> WARNING: could not write block 0 of base/1770990/t_16413137 (seg456 slice1 127.0.0.77:6006 pid=1363799)
DETAIL: Multiple failures --- write error might be permanent.
> WARNING: could not write block 0 of base/1770990/t_16413137 (seg104 slice1 127.0.0.42:6004 pid=3642779)
DETAIL: Multiple failures --- write error might be permanent.

mdp=# select count(3) from public2.table8d;

WARNING: could not write block 0 of base/1770990/t_16413137 (seg215 slice1 127.0.0.53:6005 pid=3957931)
DETAIL: Multiple failures --- write error might be permanent.
WARNING: could not write block 0 of base/1770990/t_16413137 (seg104 slice1 127.0.0.42:6004 pid=3941480)
DETAIL: Multiple failures --- write error might be permanent.

Environment

Product Version: 6.23

Resolution

This is a known issue involving temporary tables that is fixed in 6.23.3. The workaround is to restart the DB.