PG_LO_IMPORT(n)
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_importmust be called within aBEGIN/COMMITtransaction 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
- alpine 3.22: pgtcl-doc 3.1.0-r0 Β· BSD-3-Clause
- alpine 3.23: pgtcl-doc 3.1.1-r0 Β· BSD-3-Clause
- alpine 3.24: pgtcl-doc 3.1.1-r0 Β· BSD-3-Clause
- nixpkgs unstable: pgtcl 3.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms