​
Syntax

ALTER TABLE table_name
    alter_option;

alteroption depends on the operation you want to perform on the table. For all supported clauses, see the sections below.

​
Clauses

​
ADD COLUMN

ALTER TABLE table_name
    ADD [ COLUMN ] column_name data_type [ PRIMARY KEY ] [ DEFAULT default_expr ];
Parameter or clauseDescription
ADD [ COLUMN ]This clause adds a new column to the table. COLUMN is optional.
column_nameSpecify the name of the column you want to add.
data_typeThe data type of the new column.
DEFAULTThe DEFAULT clause allows you to assign a default value to a column. This default value is used when a new row is inserted, and no explicit value is provided for that column.
default_exprdefault_expr is any constant value or variable-free expression that does not reference other columns in the current table or involve subqueries. The data type of default_expr must match the data type of the column.If default_expr is impure, such as using a function like now(), all historical data will be filled with the result of the expression evaluated at the time the statement was executed. For future insertions, the default expression will be evaluated at the time of each respective insertion.
-- Add a column named "age" to a table named "employees" with a data type of integer
ALTER TABLE employees ADD age int;
  • If your table is defined with a schema registry, its columns can not be altered.
  • Columns added by this command cannot be used by any existing materialized views or indexes. You must create new materialized views or indexes to reference it.

​
DROP COLUMN

ALTER TABLE table_name
    DROP [ COLUMN ] [ IF EXISTS ] column_name;
Parameter or clauseDescription
DROP [ COLUMN ]This clause drops an existing column from a table. COLUMN is optional.
IF EXISTSDo not return an error if the specified column does not exist. A notice is issued instead.
column_nameSpecify the column you want to remove.
-- Remove a column named "fax" from the "employees" table
ALTER TABLE employees DROP fax;
  • If your table is defined with a schema registry, you can only change the table schema by ALTER TABLE t REFRESH SCHEMA. One exception is you can drop the generated columns even if the schema is defined with a schema registry. Note that dropping these generated columns will trigger a schema refresh.
  • You cannot drop columns referenced by materialized views or indexes.
  • To drop a column referenced by a generated column, you must first drop the generated column.

​
OWNER TO

ALTER TABLE table_name
    OWNER TO new_user;
Parameter or clauseDescription
OWNER TOThis clause changes the owner of the table to the specified user. It will cascadingly change all related internal objects as well, and the associated indexes will be changed too.
new_userSpecify the user you want to assign to the table.
-- Change the owner of the table named "t" to the user "user1"
ALTER TABLE t OWNER TO user1;

After setting, you can observe the parallelism status within the internal rw_table_fragments table.

​
SET SCHEMA

ALTER TABLE table_name
    SET SCHEMA schema_name;
Parameter or clauseDescription
SET SCHEMAThis clause moves the table into another schema. Associated indexes, constraints, and sequences owned by table columns are moved as well.
schema_nameSpecify the schema to which the table will be moved.
-- Move a table named "test_table" into a schema named "test_schema"
ALTER TABLE test_table SET SCHEMA test_schema;

​
SET PARALLELISM

ALTER TABLE table_name
SET PARALLELISM = parallelism_number;
Parameter or clauseDescription
SET PARALLELISMThis clause controls the degree of parallelism for the targeted streaming job.
parallelism_numberThis parameter can be ADAPTIVE or a fixed number, like 1, 2, 3, etc. Altering the parameter to ADAPTIVE will expand the streaming job’s degree of parallelism to encompass all available units, whereas setting it to a fixed number will lock the job’s parallelism at that specific figure. Setting it to 0 is equivalent to ADAPTIVE. After setting the parallelism, the parallelism status of a table can be observed within the internal rw_table_fragments table or the rw_fragmentstable.
ALTER TABLE test_table SET PARALLELISM = 8;

Here is a more detailed example for you to practise this clause:

First, let’s set the parallelism to 3 by the SET command.

SET streaming_parallelism = 3;

Then let’s create a table to view the parallelism we set. As mentioned, the parallelism status of a table can be observed within the rw_fragments table.

-- Create a table.
CREATE TABLE t(v int);
-- View parrellelism by rw_fragments table.
SELECT fragment_id, parallelism FROM rw_fragments;

------RESULTS
 fragment_id | parallelism
-------------+-------------
           1 |           3
           2 |           3
(2 rows)

Now we can use SET PARALLELISM to change the parallelism and view the change:

-- Set to a fixed number.
ALTER TABLE t SET PARALLELISM = 8;
SELECT fragment_id, parallelism FROM rw_fragments;

------RESULTS
 fragment_id | parallelism
-------------+-------------
           1 |           8
           2 |           8
(2 rows)

-- Set to ADAPTIVE
ALTER TABLE t SET PARALLELISM = adaptive;
SELECT fragment_id, parallelism FROM rw_fragments;

------RESULTS
 fragment_id | parallelism
-------------+-------------
           1 |          12
           2 |          12
(2 rows)

​
RENAME TO

ALTER TABLE table_name
    RENAME TO new_name;
Parameter or clauseDescription
RENAME TOThis clause changes the name of the table.
new_nameThe new name of the table.
-- Change the name of the table named "table0" to "table1"
ALTER TABLE table0 RENAME TO table1;

​
REFRESH SCHEMA

ALTER TABLE table_name
    REFRESH SCHEMA;

This command alters the schema registry of a table created with connectors.

-- Refresh the schema of the table named "t_user".
ALTER TABLE t_user REFRESH SCHEMA;

If a downstream fragment references a column that is either missing or has undergone a type change in the updated schema, the command will be declined.

​
SET SOURCE_RATE_LIMIT

ALTER TABLE table_name
    SET SOURCE_RATE_LIMIT { TO | = } { default | rate_limit_number };

For tables with connector, this statement controls the rate limit of the associated source. For the specific value of SOURCE_RATE_LIMIT, refer to How to view runtime parameters.

Example
-- Create a table with source
CREATE TABLE kafka_source (v1 int) WITH (
  connector = 'kafka',
  topic = 'kafka_source',
  properties.bootstrap.server = 'localhost:29092',
  scan.startup.mode = 'earliest',
  source_rate_limit = 0
) FORMAT PLAIN ENCODE JSON
Example
-- Pause the source
ALTER TABLE kafka_source SET source_rate_limit TO default;
Example
-- Alter the rate limit of this table
ALTER TABLE kafka_source SET source_rate_limit TO 1000;

​
SET BACKFILL_RATE_LIMIT

ALTER TABLE table_name
    SET BACKFILL_RATE_LIMIT { TO | = } { default | rate_limit_number };

For CDC table created from a CDC source, this statement controls the rate limit of backfilling from the CDC database. For the specific value of BACKFILL_RATE_LIMIT, refer to How to view runtime parameters.

Examples
-- Pause the backfill
ALTER TABLE t1 SET BACKFILL_RATE_LIMIT=0;

-- Alter backfill rate limit
ALTER TABLE t1 SET BACKFILL_RATE_LIMIT=1000;

-- Disable the backfill
ALTER TABLE t1 SET BACKFILL_RATE_LIMIT=DEFAULT;

Was this page helpful?

ALTER SYSTEMALTER USER