-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
GoldenGate Parallel Replicat Migration fails on INT2VECTOR conversion #95588
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Comments
jonstjohn
added
the
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
label
Jan 20, 2023
blathers-crl
bot
added
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
T-sql-queries
SQL Queries Team
labels
Jan 20, 2023
|
msirek
pushed a commit
to msirek/cockroach
that referenced
this issue
Jan 25, 2023
Fixes cockroachdb#95588 In Postgres, `array_to_string` traverses nested arrays and prints their contents. In CRDB, the nested array structures are printed out. For example, `SELECT array_to_string(ARRAY[ARRAY[ARRAY[5,6], ARRAY[2,3]]], ' ');` CRDB Result: `ARRAY[ARRAY[5:::INT8,6:::INT8],ARRAY[2:::INT8,3:::INT8]]` Postgres Result: `5 6 2 3` This fix brings the behavior of `array_to_string` in line with Postgres, and avoids printing the nested ARRAY structures. Some tools like GoldenGate rely on Postgres-compatible behavior of `array_to_string` for proper functioning. Release note (bug fix): This patch fixes the array_to_string built-in function so that nested arrays are traversed without printing 'ARRAY' at each nesting level.
craig bot
pushed a commit
that referenced
this issue
Jan 25, 2023
94180: streamingccl: don't resume job in TestTenantStreamingCutoverOnSourceFailure r=adityamaru a=stevendanna ALTER TENANT ... COMPLETE REPLICATION resumes the job for the user, so there is no need to resume the job here. This does raise the question about whether or not it is the right behaviour to resume the job by default. Fixes #94034 Release note: None 95753: roachtest: fix env var passing in activerecord test r=srosenberg a=andyyang890 This patch fixes the rails version pinning in the activerecord roachtest. The rails version is passed in via the env variable `RAILS_VERSION` and was previously being set before the `sudo` in the adapter install command and thus erroneously discarded. Informs #94211 Release note: None 95773: multiregionccl: add a missing log scope r=ajwerner a=ajwerner Epic: none Release note: None 95802: builtins: array_to_string should traverse nested arrays r=yuzefovich a=msirek Fixes #95588 In Postgres, `array_to_string` traverses nested arrays and prints their contents. In CRDB, the nested array structures are printed out. For example, `SELECT array_to_string(ARRAY[ARRAY[ARRAY[5,6], ARRAY[2,3]]], ' ');` CRDB Result: `ARRAY[ARRAY[5:::INT8,6:::INT8],ARRAY[2:::INT8,3:::INT8]]` Postgres Result: `5 6 2 3` This fix brings the behavior of `array_to_string` in line with Postgres, and avoids printing the nested ARRAY structures. Some tools like GoldenGate rely on Postgres-compatible behavior of `array_to_string` for proper functioning. Release note (bug fix): This patch fixes the array_to_string built-in function so that nested arrays are traversed without printing 'ARRAY' at each nesting level. 95824: sql/execinfrapb: remove no-effect nullable from GenerativeSplitAndScatterSpec r=rhu713 a=rhu713 Remove no-effect nullable from GenerativeSplitAndScatterSpec that was causing warning messages during build. Release note: None Co-authored-by: Steven Danna <danna@cockroachlabs.com> Co-authored-by: Andy Yang <yang@cockroachlabs.com> Co-authored-by: Andrew Werner <awerner32@gmail.com> Co-authored-by: Mark Sirek <sirek@cockroachlabs.com> Co-authored-by: Rui Hu <rui@cockroachlabs.com>
blathers-crl bot
pushed a commit
that referenced
this issue
Jan 25, 2023
Fixes #95588 In Postgres, `array_to_string` traverses nested arrays and prints their contents. In CRDB, the nested array structures are printed out. For example, `SELECT array_to_string(ARRAY[ARRAY[ARRAY[5,6], ARRAY[2,3]]], ' ');` CRDB Result: `ARRAY[ARRAY[5:::INT8,6:::INT8],ARRAY[2:::INT8,3:::INT8]]` Postgres Result: `5 6 2 3` This fix brings the behavior of `array_to_string` in line with Postgres, and avoids printing the nested ARRAY structures. Some tools like GoldenGate rely on Postgres-compatible behavior of `array_to_string` for proper functioning. Release note (bug fix): This patch fixes the array_to_string built-in function so that nested arrays are traversed without printing 'ARRAY' at each nesting level.
msirek
pushed a commit
to msirek/cockroach
that referenced
this issue
Jan 25, 2023
Fixes cockroachdb#95588 In Postgres, `array_to_string` traverses nested arrays and prints their contents. In CRDB, the nested array structures are printed out. For example, `SELECT array_to_string(ARRAY[ARRAY[ARRAY[5,6], ARRAY[2,3]]], ' ');` CRDB Result: `ARRAY[ARRAY[5:::INT8,6:::INT8],ARRAY[2:::INT8,3:::INT8]]` Postgres Result: `5 6 2 3` This fix brings the behavior of `array_to_string` in line with Postgres, and avoids printing the nested ARRAY structures. Some tools like GoldenGate rely on Postgres-compatible behavior of `array_to_string` for proper functioning. Release note (bug fix): This patch fixes the array_to_string built-in function so that nested arrays are traversed without printing 'ARRAY' at each nesting level.
Shivs11
pushed a commit
to Shivs11/cockroach
that referenced
this issue
Jan 30, 2023
Fixes cockroachdb#95588 In Postgres, `array_to_string` traverses nested arrays and prints their contents. In CRDB, the nested array structures are printed out. For example, `SELECT array_to_string(ARRAY[ARRAY[ARRAY[5,6], ARRAY[2,3]]], ' ');` CRDB Result: `ARRAY[ARRAY[5:::INT8,6:::INT8],ARRAY[2:::INT8,3:::INT8]]` Postgres Result: `5 6 2 3` This fix brings the behavior of `array_to_string` in line with Postgres, and avoids printing the nested ARRAY structures. Some tools like GoldenGate rely on Postgres-compatible behavior of `array_to_string` for proper functioning. Release note (bug fix): This patch fixes the array_to_string built-in function so that nested arrays are traversed without printing 'ARRAY' at each nesting level.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Describe the problem
When Oracle GoldenGate is used to migrate an Oracle database to CRDB using the PostgreSQL driver in parallel replicat mode, it fails with a type conversion error. This appears to occur when a compound primary key is used in the CRDB target database and was traced to a problem with INT2VECTOR conversion.
This ticket is not specifically to address GoldenGate working in parallel replicat mode, but to fix the INT2VECTOR conversion discrepancy between PostgreSQL and CRDB.
To Reproduce
The simplest possible reproduction of the issue is to run the following query in PostgreSQL and CRDB:
In PostgreSQL, the following output is observed:
In CRDB, the following is observed:
The type conversion error in CRDB can be produced by running the following query:
Whereas in PostgreSQL, this same query produces this result:
Expected behavior
INT2VECTOR conversion has the same result in PostgreSQL and CRDB.
Additional data / screenshots
The original query produced by GoldenGate that exhibited this issue was:
To reproduce the error using this query, it is necessary to create a table in the current database
tbl
with a compound primary key, e.g.:Environment:
Additional context
The result is that GoldenGate cannot be run in parallel replicat mode.
Jira issue: CRDB-23601
The text was updated successfully, but these errors were encountered: