You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current YSQL COPY preserves the Postgres semantics by wrapping all of the inserts in a single large transaction. There are a few outstanding issues with large-write distributed transactions in YB (#1875#1923), so it may be better to introduce a non-transactional variant of COPY for use when it is not imperative to provide isolation/atomicity (e.g. when loading DB for first time before workloads are run on it).
The text was updated successfully, but these errors were encountered:
Summary: This diff adds support for non-transactional COPY. It can be enabled using `--tserver_flags "ysql_non_txn_copy=true"`.
Test Plan:
Manual verification:
- Through logging verified we followed non-txn insert path when GFLAG was true and followed txn insert path when GFLAG was false.
- Verified that when performing COPY count_intents was 0 when GFLAG was true, and was non-zero when GFLAG was false.
Reviewers: mihnea, neha
Reviewed By: neha
Subscribers: yql
Differential Revision: https://phabricator.dev.yugabyte.com/D7185
The current YSQL
COPY
preserves the Postgres semantics by wrapping all of the inserts in a single large transaction. There are a few outstanding issues with large-write distributed transactions in YB (#1875 #1923), so it may be better to introduce a non-transactional variant of COPY for use when it is not imperative to provide isolation/atomicity (e.g. when loading DB for first time before workloads are run on it).The text was updated successfully, but these errors were encountered: