Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assert: insert AO table with returning ctid #14759

Closed
huiliang-liu opened this issue Jan 11, 2023 · 3 comments
Closed

Assert: insert AO table with returning ctid #14759

huiliang-liu opened this issue Jan 11, 2023 · 3 comments

Comments

@huiliang-liu
Copy link
Member

Bug Report

Failed assertion if insert data into an AO table with returning ctid

Greenplum version or build

Greenplum Database 6.23.0

OS version and uname -a

centos7, Linux 3.10.0-1160.24.1.el7.x86_64

autoconf options used ( config.status --config )

Installation information ( pg_config )

Expected behavior

insert successfully and return the ctid

Actual behavior

ERROR: Unexpected internal error (execTuples.c:1583) (seg2 slice2 10.117.190.244:7002 pid=15933) (execTuples.c:1583)
DETAIL: FailedAssertion("!(((bool) (((const void*)(&(slot->PRIVATE_tts_synthetic_ctid)) != ((void *)0)) && ((&(slot->PRIVATE_tts_synthetic_ctid))->ip_posid != 0))))", File: "execTuples.c", Line: 1583)
HINT: Process 15933 will wait for gp_debug_linger=120 seconds before termination.
Note that its locks and other resources will not be released until then.

Step to reproduce the behavior

gpadmin=# CREATE TABLE returning_ctid_ao (f1 serial, f2 text) WITH (appendonly=true) DISTRIBUTED BY (f1);
CREATE TABLE
gpadmin=# INSERT INTO returning_ctid_ao(f2) VALUES ('test1') RETURNING ctid;
ERROR:  Unexpected internal error (execTuples.c:1583)  (seg2 slice2 10.117.190.244:7002 pid=15933) (execTuples.c:1583)
DETAIL:  FailedAssertion("!(((bool) (((const void*)(&(slot->PRIVATE_tts_synthetic_ctid)) != ((void *)0)) && ((&(slot->PRIVATE_tts_synthetic_ctid))->ip_posid != 0))))", File: "execTuples.c", Line: 1583)
HINT:  Process 15933 will wait for gp_debug_linger=120 seconds before termination.
Note that its locks and other resources will not be released until then.
@kainwen
Copy link
Contributor

kainwen commented Jan 11, 2023

Does main branch have the issue?

@huiliang-liu
Copy link
Member Author

Does main branch have the issue?

No, main branch doesn't have this issue. And AOCO table on gpdb6 works well too

@kainwen
Copy link
Contributor

kainwen commented Jan 31, 2023

Fixed by #14771

@kainwen kainwen closed this as completed Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants