PG_LO_IMPORT(n)

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

PG_LO_IMPORT() πŸ’…βœ¨

okay so this page is straight out of the PostgreSQL Tcl Interface Documentation, and it’s all about pg_lo_import β€” no cap. think β€œfile goes in, large object comes out” vibes. let’s get into it 🫢


✨ NAME ✨

pg_lo_import β€” import a large object from a file

πŸŽ€ SYNOPSIS πŸŽ€

pg_lo_import conn filename

πŸ’– DESCRIPTION πŸ’–

pg_lo_import reads the specified file and places the contents into a new large object. literally, that’s the whole mood. πŸ“₯➑️🫧

🌸 ARGUMENTS 🌸

  • conn β€” the handle of a connection to the database in which to create the large object.
  • filename β€” specifies the file from which to import the data. yes bestie, that’s where the bytes are coming from πŸ“

πŸ¦‹ RETURN VALUE πŸ¦‹

the OID of the large object created. that’s the little receipt of your new large object, iykyk πŸ’…

⭐ NOTES ⭐

pg_lo_import must be called within a BEGIN/COMMIT transaction block. no cap, don’t skip this one β€” it’s giving mandatory wrap energy πŸ”₯

and that’s the whole page, bestie πŸŽ€ this was the pg_lo_import manual page from the PostgreSQL Tcl Interface Documentation, dated 17 September 2020 β€” mwah, bye πŸ’–

πŸ“¦ where this page comes from