ALTER_LARGE_OBJECT(7pg17)

💅 NAME 💅

okay so welcome to the ALTER LARGE OBJECT(7) page — that’s the ALTER_LARGE_OBJECT(7pg17) one if you’re peeking at the filename, bestie. This is the manual for changing the definition of a large object. iconic little admin moment. ✨

🎀 SYNOPSIS 🎀

ALTER LARGE OBJECT large_object_oid OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }

🦋 DESCRIPTION 🦋

ALTER LARGE OBJECT changes the definition of a large object. That’s the whole main-character move, no cap. 💫

You must own the large object to use ALTER LARGE OBJECT. And to alter the owner, you also have to be able to SET ROLE to the new owning role. both of those, bestie — yes, both. 🙈 (However, a superuser can alter any large object anyway, because superuser privileges stay iconic like that. 👑)

Currently, the only functionality is to assign a new owner, so both restrictions always apply. Fr fr. 💀

🌸 PARAMETERS 🌸

• large_object_oid — the OID of the large object to be altered. That’s the one getting the makeover. 🎀
• new_owner — the new owner of the large object. Hand over the keys, bestie. 🔑

🌈 COMPATIBILITY 🌈

There is no ALTER LARGE OBJECT statement in the SQL standard. It’s just not there, and that’s the tea. 😭

🫶 SEE ALSO 🫶

• Chapter 33 — go read it, iykyk. 📚

💖 sign-off time: this page is from PostgreSQL 17.11, dated 2026, and it’s literally the ALTER LARGE OBJECT(7) manual. Slay. 💅✨