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

[docs] revised statement in bulk export to mention PK support #16198

Merged
merged 3 commits into from
Feb 27, 2023
Merged

[docs] revised statement in bulk export to mention PK support #16198

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0978204
revised statement
aishwarya24 Feb 22, 2023
5872b71
Merge branch 'master' into docs/table-update
aishwarya24 Feb 27, 2023
9acb47d
changes in stable
aishwarya24 Feb 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/preview/manage/data-migration/bulk-export-ysql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The `ysql_dump` tool can simplify some steps of your schema migration, refer to

### Specify `PRIMARY KEY` inline

YugabyteDB (as of v2.2) does not support the PostgreSQL syntax of first declaring a table, and subsequently running an ALTER TABLE command to add the primary key. This is because the data in YugabyteDB tables are index-organized according to the primary key specification. There is a significant performance difference in a distributed SQL database between a table that is organized by row ID with an added primary key constraint, versus a table whose data layout is index-organized from the get go.
YugabyteDB supports the PostgreSQL syntax of first declaring a table, and subsequently running an ALTER TABLE command to add the primary key. Note that the ALTER TABLE operation requires a disk re-write and may be resource intensive, so it is recommended to set the primary key inline as part of the CREATE TABLE operation.

### Use `HASH` sort order

Expand Down
2 changes: 1 addition & 1 deletion docs/content/stable/manage/data-migration/bulk-export-ysql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The `ysql_dump` tool can simplify some steps of your schema migration, refer to

### Specify `PRIMARY KEY` inline

YugabyteDB (as of v2.2) does not support the PostgreSQL syntax of first declaring a table, and subsequently running an ALTER TABLE command to add the primary key. This is because the data in YugabyteDB tables are index-organized according to the primary key specification. There is a significant performance difference in a distributed SQL database between a table that is organized by row ID with an added primary key constraint, versus a table whose data layout is index-organized from the get go.
YugabyteDB supports the PostgreSQL syntax of first declaring a table, and subsequently running an ALTER TABLE command to add the primary key. Note that the ALTER TABLE operation requires a disk re-write and may be resource intensive, so it is recommended to set the primary key inline as part of the CREATE TABLE operation.

### Use `HASH` sort order

Expand Down