ALTER_LARGE_OBJECT(7pg16)
π ALTER_LARGE_OBJECT: PostgreSQL 16.15 Documentation, section 7 π
Okay bestie, welcome to ALTER LARGE OBJECT β aka the ALTER_LARGE_OBJECT page from the PostgreSQL 16.15 Documentation. Section 7 is serving main-character energy today, and we're gonna make large-object ownership make sense. π«Ά
β¨ NAME β¨
ALTER_LARGE_OBJECT - change the definition of a large object. That's the whole assignment, and it ate. π
π SYNOPSIS π
ALTER LARGE OBJECT large_object_oid OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
π DESCRIPTION π
Okay so ALTER LARGE OBJECT changes the definition of a large object. Lowkey iconic. β¨
You must own the large object to use ALTER LARGE OBJECT. To alter the owner, you must also be able to SET ROLE to the new owning role. (But ngl, a superuser can alter any large object anyway.) Currently, the only functionality is to assign a new owner, so both restrictions always apply β periodt. π
π«Ά PARAMETERS π«Ά
large_object_oidβ OID of the large object to be alterednew_ownerβ The new owner of the large object
π COMPATIBILITY π
There is no ALTER LARGE OBJECT statement in the SQL standard β not a single one, bestie. π
π SEE ALSO π
Chapter 35 β go read it, bestie. Iykyk. π¦
π That's the tea from PostgreSQL 16.15, dated 2026 β manual page out, bestie. π
π¦ where this page comes from
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms