ALTER_FOREIGN_DATA_WRAPPER(7pg13)

💅 ALTER_FOREIGN_DATA_WRAPPER(7pg13) 💅

okay bestie, this is the ALTER_FOREIGN_DATA_WRAPPER(7pg13) page from the PostgreSQL 13.23 docs. Buckle up, we're changing foreign-data wrapper definitions and being iconic about it. 🦋

---

✨ NAME ✨

ALTER_FOREIGN_DATA_WRAPPER — change the definition of a foreign-data wrapper

---

🎀 SYNOPSIS 🎀

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 the generic options of the foreign-data wrapper — and yes, at least one clause is required. The second form changes the owner of the foreign-data wrapper.

Only superusers can alter foreign-data wrappers. Additionally, only superusers can own foreign-data wrappers. that's the rule, no cap. 👑

---

🦋 PARAMETERS 🦋

• name — the name of an existing foreign-data wrapper. got it? good. 💖
• HANDLER handler_function — specifies a new handler function for the foreign-data wrapper. slay, new handler. ✨
• NO HANDLER — used to specify that the foreign-data wrapper should no longer have a handler function.

bestie, warning: foreign tables that use a foreign-data wrapper with no handler cannot be accessed. like, at all. 💀

• VALIDATOR validator_function — specifies a new validator function for the foreign-data wrapper.

okay so this is the messy part: it is possible that pre-existing options of the foreign-data wrapper, or of dependent servers, user mappings, or foreign tables, are invalid according to the new validator. PostgreSQL does not check for this. It is up to the user to make sure that these options are correct before using the modified foreign-data wrapper. However, any options specified in this ALTER FOREIGN DATA WRAPPER command will be checked using the new validator. 🙈

• NO VALIDATOR — used to specify that the foreign-data wrapper should no longer have a validator function.
• OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] ) — change options for the foreign-data wrapper. ADD, SET, and DROP specify the action to be performed. ADD is assumed if no operation is explicitly specified. Option names must be unique; names and values are also validated using the foreign data wrapper's validator function, if any. 🎀
• new_owner — the user name of the new owner of the foreign-data wrapper.
• new_name — the new name for the foreign-data wrapper.

---

🧚 EXAMPLES 🧚

Change a foreign-data wrapper dbi, add option foo, drop bar:

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

Change the foreign-data wrapper dbi validator to bob.myvalidator:

ALTER FOREIGN DATA WRAPPER dbi VALIDATOR bob.myvalidator;

---

🌈 COMPATIBILITY 🌈

ALTER FOREIGN DATA WRAPPER conforms to ISO/IEC 9075-9 (SQL/MED), except that the HANDLER, VALIDATOR, OWNER TO, and RENAME clauses are extensions. iykyk. ✨

---

💜 SEE ALSO 💜

• CREATE FOREIGN DATA WRAPPER (CREATE_FOREIGN_DATA_WRAPPER(7))
• DROP FOREIGN DATA WRAPPER (DROP_FOREIGN_DATA_WRAPPER(7))

---

kisses and sparkles, bestie: PostgreSQL 13.23 💖, dated 2025 ✨ — and the footer gremlin says ALTER FOR...A WRAPPER(7). periodt. 🫶