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

Performance Guide: Prefer CTAS to ALTER TABLE #3060

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Performance Guide: Prefer CTAS to ALTER TABLE #3060

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions docs/guides/performance/schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,3 +84,7 @@ We illustrate the effect of using primary keys with the [LDBC Comment table at s
In this case, primary keys will only have a (small) positive effect on highly selective queries such as when filtering on a single identifier. They do not have an effect on join and aggregation operators.

> Bestpractice For best bulk load performance, avoid defining primary key constraints if possible.

## Schema Changes

When making changes to the schema, prefer using [`CREATE TABLE ... AS SELECT`](../../sql/statements/create_table#create-table--as-select-ctas) to [`ALTER TABLE`](../../sql/statements/alter_table).