-
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] Feature Support - Transaction Control Commands #1125
Comments
|
I'd like to see this, my particular use case is for automated migrations. |
Would be nice to have this for pgloader, which uses
|
|
This is the golang code I ended up writing for transactions. Since SAVEPOINT is not yet there in YB, I have to retry the transaction from scratch(if it is a retryable error) instead of a SAVEPOINT. |
|
+1'ed due to the Sequel (http://sequel.jeremyevans.net/) library's use of savepoints |
+1'ed SavePoint is crucial for my application. |
+1 SAVEPOINT is widely used in RoR test suites as transactional_fixtures or database_cleaner.strategy :transaction. So right now I have no confidence in Yugabyte compatibility with my legacy application (postgresql). As a workaround I can use strategy :deletion but that slows test suites execution time. |
I also need this to use txdb for my tests. |
https://mikro-orm.io/ migrations |
+1'ed SavePoint is crucial for my application.
|
I using Postgraphile and when I add data to yugabyte database see error: |
@trfi please check the logs of Postgraphile or increase the verbosity of debug log to get more info regarding the error. |
SAVEPOINT would also be very helpful for migrations and unittests in Django |
This blocks people from using amazon's database migration tool properly to replicate from postgresql to yugabytedb |
@kulminaator -- which specific statement or statements are you referring to? Please note - we recently added support for savepoints and rollback to savepoints. CC: @robertsami |
Summary: Undeprecate --enable_pg_savepoint flag to implement JIRA issue https://yugabyte.atlassian.net/browse/DB-5396. This flag was originally deprecated in https://phabricator.dev.yugabyte.com/D13260 Note that the error message the user will see is: ``` Bad status: Network error (yb/yql/pgwrapper/libpq_utils.cc:329): Execute of 'SAVEPOINT A' failed: 7, message: ERROR: SAVEPOINT <transaction> not supported yet LINE 1: SAVEPOINT A ^ HINT: See #1125. React with thumbs up to raise its priority (pgsql error 0A000) (aux msg ERROR: SAVEPOINT <transaction> not supported yet ``` Test Plan: Added a test to verify that setting this flag to false causes SAVEPOINT to produce an error. ``` yb_build.sh --sj --cxx-test pgwrapper_pg_mini-test --gtest_filter '*TestSavePointCanBeDisabled*' ``` Reviewers: hsunder, jhe, slingam Reviewed By: slingam Differential Revision: https://phabricator.dev.yugabyte.com/D23455
…pted when disabled by --enable_pg_savepoint Summary: When this flag is set to false, use of SAVEPOINT related features in SQL produces an error like: ``` 2023-03-15 23:47:51.117 UTC [722541] ERROR: SAVEPOINT <transaction> not supported yet at character 1 2023-03-15 23:47:51.117 UTC [722541] HINT: See #1125. React with thumbs up to raise its priority ``` This is misleading because it implies the entire feature is not yet supported whereas it's just unsupported because of gflag setting. Also, the issue pointed to above (1125) -- #1125 -- seems to be out of date because it claims that many implemented features are still unimplemented. This diff changes the error message to: ``` 2023-03-15 23:32:20.676 UTC [680415] ERROR: SAVEPOINT <transaction> not supported due to setting of flag --enable_pg_savepoints at character 1 ``` 3/29/2023 UPDATE: error message is now: ``` ERROR: SAVEPOINT <transaction> not supported due to setting of flag --enable_pg_savepoints LINE 1: SAVEPOINT A ^ HINT: flag may have set to false because savepoints do not currently work with xCluster replication (see #14308) ``` Fixes #16374 Test Plan: ``` yb_build.sh --sj --cxx-test pgwrapper_pg_mini-test --gtest_filter '*TestSavePointCanBeDisabled*' ``` Look at error message in test log. 3/29/2023 UPDATE: replace that test with one that checks the error message: ``` yb_build.sh --java-test org.yb.pgsql.TestPgSavepoints ``` Reviewers: slingam, jhe, rsami, hsunder Reviewed By: hsunder Subscribers: ybase, rsami Differential Revision: https://phabricator.dev.yugabyte.com/D23625
…is attempted when disabled by --enable_pg_savepoint Summary: When this flag is set to false, use of SAVEPOINT related features in SQL produces an error like: ``` 2023-03-15 23:47:51.117 UTC [722541] ERROR: SAVEPOINT <transaction> not supported yet at character 1 2023-03-15 23:47:51.117 UTC [722541] HINT: See yugabyte#1125. React with thumbs up to raise its priority ``` This is misleading because it implies the entire feature is not yet supported whereas it's just unsupported because of gflag setting. Also, the issue pointed to above (1125) -- yugabyte#1125 -- seems to be out of date because it claims that many implemented features are still unimplemented. This diff changes the error message to: ``` 2023-03-15 23:32:20.676 UTC [680415] ERROR: SAVEPOINT <transaction> not supported due to setting of flag --enable_pg_savepoints at character 1 ``` 3/29/2023 UPDATE: error message is now: ``` ERROR: SAVEPOINT <transaction> not supported due to setting of flag --enable_pg_savepoints LINE 1: SAVEPOINT A ^ HINT: flag may have set to false because savepoints do not currently work with xCluster replication (see yugabyte#14308) ``` Fixes yugabyte#16374 Test Plan: ``` yb_build.sh --sj --cxx-test pgwrapper_pg_mini-test --gtest_filter '*TestSavePointCanBeDisabled*' ``` Look at error message in test log. 3/29/2023 UPDATE: replace that test with one that checks the error message: ``` yb_build.sh --java-test org.yb.pgsql.TestPgSavepoints ``` Reviewers: slingam, jhe, rsami, hsunder Reviewed By: hsunder Subscribers: ybase, rsami Differential Revision: https://phabricator.dev.yugabyte.com/D23625
Jira Link: DB-1016
The following transaction control commands are not yet supported.
As well as savepoint related commands: #9219
The text was updated successfully, but these errors were encountered: