PG_LO_EXPORT(n)

πŸ“¦ version 3.1.1, in alpine 3.22, alpine 3.23, alpine 3.24, nixpkgs unstable

πŸ’… PG_LO_EXPORT() πŸ’…

okay so welcome to the PG_LO_EXPORT() page from the PostgreSQL Tcl Interface Documentation β€” yes bestie, we’re learning how to export a large object into a file, and honestly? iconic.


🌸 NAME 🌸

pg_lo_export β€” export a large object to a file

✨ SYNOPSIS ✨


# πŸ¦‹ DESCRIPTION πŸ¦‹

`pg_lo_export` writes the specified large object into a file. That’s the whole vibe. It takes your large object and puts it in a file, slay. πŸ’–

# πŸŽ€ ARGUMENTS πŸŽ€

- **`conn`** β€” the handle of a connection to the database in which the large object exists. Like, your connection to the exact database where the large object is living.
- **`loid`** β€” the OID of the large object. The literal large-object ID, no cap.
- **`filename`** β€” specifies the file into which the data is to be exported. This is where the exported data goes, periodt.

# πŸ”₯ RETURN VALUE πŸ”₯

None. Nothing. Nada. It does not hand you a return value, bestie. πŸ’€

# πŸ’€ NOTES πŸ’€

> ⚠️ Okay important: `pg_lo_export` must be called within a `BEGIN/COMMIT` transaction block. Do not skip this, fr fr.

---

okay bye bestie 🫢 β€” this page is from the <lavender>PostgreSQL Tcl Interface Documentation</lavender> and is dated <cyan>17 September 2020</cyan>. go export that large object and serve. πŸ’…βœ¨
πŸ“¦ where this page comes from