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.

Sign up for GitHub

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

Jump to bottom

[YSQL] Ensure no kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size (gflag with default of 256KB). #11572

Open
pkj415 opened this issue Feb 23, 2022 · 0 comments
Open

[YSQL] Ensure no kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size (gflag with default of 256KB). #11572

pkj415 opened this issue Feb 23, 2022 · 0 comments
Assignees
@pkj415
Labels
2024.1.1_blocker area/docdb YugabyteDB core features area/ysql Yugabyte SQL (YSQL) kind/enhancement This is an enhancement of an existing feature pg-compatibility Label for issues that result in differences b/w YSQL and Pg semantics priority/medium Medium priority issue

Comments

@pkj415
Copy link
Contributor

pkj415 commented Feb 23, 2022 •
edited

Jira Link: DB-508

Description

Ensure no kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size and results in flushing before a kReadRestart/kConflict error is hit.

We need to solve this only if #11573 will not be solved, else this will be solved implicitly.
@pkj415 pkj415 added the area/ysql Yugabyte SQL (YSQL) label Feb 23, 2022
@pkj415 pkj415 mentioned this issue Feb 23, 2022
Open
@pkj415 pkj415 changed the title [YSQL] Ensure no kReadRestart/kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size. [YSQL] Ensure no kReadRestart/kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size (gflag with default of 256KB). Feb 23, 2022
@m-iancu m-iancu mentioned this issue Mar 7, 2022
Closed
@pkj415 pkj415 added the pg-compatibility Label for issues that result in differences b/w YSQL and Pg semantics label May 24, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels May 24, 2022
@pkj415 pkj415 mentioned this issue Jul 28, 2022
Open
@pkj415 pkj415 mentioned this issue Aug 9, 2022
Open
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature and removed kind/bug This issue is a bug labels Sep 14, 2022
@robertsami robertsami added this to Needs Triage in Wait-Queue Based Locking via automation Jul 27, 2023
@robertsami robertsami moved this from Needs Triage to EA Blocking in Wait-Queue Based Locking Jul 27, 2023
@robertsami robertsami moved this from EA Blocking to Needs Triage in Wait-Queue Based Locking Jul 28, 2023
@sushantrmishra sushantrmishra removed this from Needs Triage in Wait-Queue Based Locking Aug 10, 2023
@sushantrmishra sushantrmishra self-assigned this Aug 10, 2023
@yugabyte-ci yugabyte-ci added priority/highest Highest priority issue and removed priority/medium Medium priority issue labels Aug 31, 2023
@yugabyte-ci yugabyte-ci added priority/high High Priority and removed priority/highest Highest priority issue labels Nov 15, 2023
@pkj415 pkj415 mentioned this issue Dec 18, 2023
Open
1 task
@pkj415 pkj415 changed the title [YSQL] Ensure no kReadRestart/kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size (gflag with default of 256KB). [YSQL] Ensure no kConflict errors are thrown in a READ COMMITTED txn even if statement's output exceeds ysql_output_buffer_size (gflag with default of 256KB). Dec 18, 2023
@rthallamko3 rthallamko3 added the area/docdb YugabyteDB core features label Dec 18, 2023
@yugabyte-ci yugabyte-ci added priority/medium Medium priority issue and removed priority/high High Priority labels Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pkj415 pkj415

Labels
2024.1.1_blocker area/docdb YugabyteDB core features area/ysql Yugabyte SQL (YSQL) kind/enhancement This is an enhancement of an existing feature pg-compatibility Label for issues that result in differences b/w YSQL and Pg semantics priority/medium Medium priority issue
Projects
Wait-Queue Based Locking
Status: No status
Milestone
No milestone
Development

No branches or pull requests
5 participants
@sushantrmishra @pkj415 @rthallamko3 @yugabyte-ci @basavaraj29