---
title: "ALTER FOREIGN DATA WRAPPER"
source: https://cloudberry.apache.org/docs/sql-stmts/alter-foreign-data-wrapper
---

# ALTER FOREIGN DATA WRAPPER

Changes the definition of a foreign-data wrapper.

## Synopsis

```sql
ALTER FOREIGN DATA WRAPPER <name>
    [ HANDLER <handler_function> | NO HANDLER ]
    [ VALIDATOR <validator_function> | NO VALIDATOR ]
    [ OPTIONS ( [ ADD | SET | DROP ] <option> ['<value>'] [, ... ] ) ]

ALTER FOREIGN DATA WRAPPER <name> OWNER TO { <new_owner> | CURRENT_USER | SESSION_USER }
ALTER FOREIGN DATA WRAPPER <name> RENAME TO <new_name>
```

## Description

`ALTER FOREIGN DATA WRAPPER` changes the definition of a foreign-data wrapper. The first form of the command changes the support functions or generic options of the foreign-data wrapper. Apache Cloudberry requires at least one clause. The second and third forms of the command change the owner or name of the foreign-data wrapper.

Only superusers can alter foreign-data wrappers. Additionally, only superusers can own foreign-data wrappers

## Parameters

**`name`**

The name of an existing foreign-data wrapper.

**`HANDLER handler_function`**

Specifies a new handler function for the foreign-data wrapper.

**`NO HANDLER`**

Specifies that the foreign-data wrapper should no longer have a handler function.

> **Note** You cannot access a foreign table that uses a foreign-data wrapper with no handler.

**`VALIDATOR validator_function`**

Specifies a new validator function for the foreign-data wrapper.

Note that it is possible that pre-existing options of the foreign-data wrapper, or of dependent servers, user mappings, or foreign tables, may become invalid when you change the validator function. Apache Cloudberry does not check for this. You must make sure that these options are correct before using the modified foreign-data wrapper. However, Apache Cloudberry will check any options specified in this `ALTER FOREIGN DATA WRAPPER` command using the new validator.

**`NO VALIDATOR`**

Specifies that the foreign-data wrapper should no longer have a validator function.

**`OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )`**

Change the foreign-data wrapper's options. `ADD`, `SET`, and `DROP` specify the action to perform. If no operation is explicitly specified, the default operation is `ADD`. Option names must be unique. Apache Cloudberry validates names and values using the foreign-data wrapper's validator function, if any.

**`OWNER TO new_owner`**

Specifies the user name of the new owner of the foreign-data wrapper. Only superusers can own foreign-data wrappers.

**`RENAME TO new_name`**

Specifies the new name of the foreign-data wrapper.

## Examples

Change the definition of a foreign-data wrapper named `dbi` by adding a new option named `foo`, and removing the option named `bar`:

```sql
ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP 'bar');
```

Change the validator function for a foreign-data wrapper named `dbi` to `bob.myvalidator`:

```sql
ALTER FOREIGN DATA WRAPPER dbi VALIDATOR bob.myvalidator;
```

## Compatibility

`ALTER FOREIGN DATA WRAPPER` conforms to ISO/IEC 9075-9 (SQL/MED), with the exception that the `HANDLER`, `VALIDATOR`, `OWNER TO`, and `RENAME TO` clauses are Apache Cloudberry extensions.

## See also

[CREATE FOREIGN DATA WRAPPER](/docs/sql-stmts/create-foreign-data-wrapper.md), [DROP FOREIGN DATA WRAPPER](/docs/sql-stmts/drop-foreign-data-wrapper.md)