-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[YSQL] Updating existing table from temp table fails #9572
Labels
area/ysql
Yugabyte SQL (YSQL)
kind/bug
This issue is a bug
pgcm
priority/medium
Medium priority issue
Comments
ijungmann
changed the title
[YSQL] Update from temp table fails
[YSQL] Updating existing table from temp table fails
Aug 3, 2021
On debug build, postgres crashes.
Postgres logs:
Backtrace on the core file:
|
fizaaluthra
pushed a commit
that referenced
this issue
Sep 15, 2021
…tions when preparing target list Summary: Presently, when iterating through the row-marked relations to add the necessary columns to the target list, we determined whether to get the YB TID or the CTID based on the target relation. However, this check should be done using the row-marked relation instead. The previous version of the code fails to work when the target relation is a YB relation and the row-marked relation is a temporary relation. (Eg: `UPDATE test1 SET z = 2 FROM test2 WHERE test1.x = test2.x;` where test2 is a temporary relation and test1 is a YB relation) Test Plan: Run `TestPgRegressFeature` to execute `yb_feature_temp` Reviewers: mihnea, amartsinchyk Reviewed By: amartsinchyk Differential Revision: https://phabricator.dev.yugabyte.com/D12994
fizaaluthra
pushed a commit
that referenced
this issue
Sep 21, 2021
…ow-marked relations when preparing target list Summary: Presently, when iterating through the row-marked relations to add the necessary columns to the target list, we determined whether to get the YB TID or the CTID based on the target relation. However, this check should be done using the row-marked relation instead. The previous version of the code fails to work when the target relation is a YB relation and the row-marked relation is a temporary relation. (Eg: `UPDATE test1 SET z = 2 FROM test2 WHERE test1.x = test2.x;` where test2 is a temporary relation and test1 is a YB relation) Original Commit: [[ f148418 | f148418 ]] Original Differential Revision: https://phabricator.dev.yugabyte.com/D12994 Test Plan: Jenkins: rebase: 2.6 Run `TestPgRegressFeature` to execute `yb_feature_temp` Reviewers: mihnea, amartsinchyk Reviewed By: amartsinchyk Differential Revision: https://phabricator.dev.yugabyte.com/D13108
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ysql
Yugabyte SQL (YSQL)
kind/bug
This issue is a bug
pgcm
priority/medium
Medium priority issue
Jira Link: DB-1936
Creating a temporary table from an existing table and then attempting to update the existing table with data from the new temporary table fails due to
variable not found in subplan target lists
. This issue does not occur when referencing another permanent table, it only seems to occur with the temporary table. Below is a reduced example of this setup.The text was updated successfully, but these errors were encountered: