(No version information available, might only be in Git) Truncates a large object bool pg_lo_truncate ( resource $large_object, int $size ) pg_lo_truncate() truncates a large object resource. To use the large object interface, it is necessary to enclose it within a transaction block. Parameters: large_object PostgreSQL large object (LOB) resource, returned by pg_lo_op

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Returns current seek position a of large object int pg_lo_tell ( resource $large_object ) pg_lo_tell() returns the current position (offset from the beginning) of a large object. To use the large object interface, it is necessary to enclose it within a transaction block. Parameters: large_object PostgreSQL large object (LOB) resource,

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Seeks position within a large object bool pg_lo_seek ( resource $large_object, int $offset [, int $whence = PGSQL_SEEK_CUR ] ) pg_lo_seek() seeks a position within a large object resource. To use the large object interface, it is necessary to enclose it within a transaction block. Parameters: large_object PostgreSQL large object (LOB

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Read a large object string pg_lo_read ( resource $large_object [, int $len = 8192 ] ) pg_lo_read() reads at most len bytes from a large object and returns it as a string. To use the large object interface, it is necessary to enclose it within a transaction block. Note: This function used to be called pg_loread(). Parameters: large_object

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Reads an entire large object and send straight to browser int pg_lo_read_all ( resource $large_object ) pg_lo_read_all() reads a large object and passes it straight through to the browser after sending all pending headers. Mainly intended for sending binary data like images or sound. To use the large object interface, it is necessary to enclose it within a transaction block. Note: Th

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Open a large object resource pg_lo_open ( resource $connection, int $oid, string $mode ) pg_lo_open() opens a large object in the database and returns large object resource so that it can be manipulated. To use the large object interface, it is necessary to enclose it within a transaction block. Note: This function used to be called pg_loopen(). Parameters:

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Import a large object from file int pg_lo_import ([ resource $connection ], string $pathname [, mixed $object_id ] ) pg_lo_import() creates a new large object in the database using a file on the filesystem as its data source. To use the large object interface, it is necessary to enclose it within a transaction block. Note: When safe mode is enabled, PHP checks whether the files or directo

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Export a large object to file bool pg_lo_export ([ resource $connection ], int $oid, string $pathname ) pg_lo_export() takes a large object in a PostgreSQL database and saves its contents to a file on the local filesystem. To use the large object interface, it is necessary to enclose it within a transaction block. Note: This function used to be called pg_loexport(). P

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Create a large object int pg_lo_create ([ resource $connection [, mixed $object_id ]] ) int pg_lo_create ( mixed $object_id ) pg_lo_create() creates a large object and returns the OID of the large object. PostgreSQL access modes INV_READ, INV_WRITE, and INV_ARCHIVE are not supported, the object is created always with both read and write access. INV_ARCHIVE has been removed from PostgreSQL i

(PHP 4 >= 4.2.0, PHP 5, PHP 7) Close a large object bool pg_lo_close ( resource $large_object ) pg_lo_close() closes a large object. large_object is a resource for the large object from pg_lo_open(). To use the large object interface, it is necessary to enclose it within a transaction block. Note: This function used to be called pg_loclose(). Parameters: result