[YSQL] Distinguish temp and foreign tables for batch COPY #11633
Assignees
Labels
area/ysql
Yugabyte SQL (YSQL)
Comments
tedyu
added a commit
that referenced
this issue
Mar 3, 2022
Summary: In CopyFrom(), currently we regard non-YB table as TEMP table. However, this produces confusing message for FOREIGN table: ``` ts1|pid52548|:30139 2022-03-01 09:16:20.854 UTC [52764] WARNING: Batched COPY is not supported on temporary tables. Defaulting to using one transaction for the entire copy. ``` This revision checks the Relation type and uses proper table type in the message. Test Plan: ybd --java-test 'org.yb.pgsql.TestPgRegressContribPostgresFdw#schedule' Reviewers: ena, myang Reviewed By: myang Subscribers: yql Differential Revision: https://phabricator.dev.yugabyte.com/D15734
jayant07-yb
pushed a commit
to jayant07-yb/yugabyte-db
that referenced
this issue
Mar 8, 2022
Summary: In CopyFrom(), currently we regard non-YB table as TEMP table. However, this produces confusing message for FOREIGN table: ``` ts1|pid52548|:30139 2022-03-01 09:16:20.854 UTC [52764] WARNING: Batched COPY is not supported on temporary tables. Defaulting to using one transaction for the entire copy. ``` This revision checks the Relation type and uses proper table type in the message. Test Plan: ybd --java-test 'org.yb.pgsql.TestPgRegressContribPostgresFdw#schedule' Reviewers: ena, myang Reviewed By: myang Subscribers: yql Differential Revision: https://phabricator.dev.yugabyte.com/D15734
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In CopyFrom(), currently we regard non-YB table as TEMP table.
However, this produces confusing message for FOREIGN table:
This revision checks the Relation type and uses proper table type in the message.
The text was updated successfully, but these errors were encountered: