1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-03 20:02:46 +03:00

Doc: fix typos.

"PGcon" should be "PGconn".  Noted by D. Frey.

Discussion: https://postgr.es/m/163191739352.4680.16994248583642672629@wrigleys.postgresql.org
This commit is contained in:
Tom Lane
2021-09-19 11:36:53 -04:00
parent 639d731acc
commit 61fb2b98f9

View File

@ -437,7 +437,7 @@ pg_int64 lo_tell64(PGconn *conn, int fd);
<indexterm><primary>lo_truncate</></> <indexterm><primary>lo_truncate</></>
To truncate a large object to a given length, call To truncate a large object to a given length, call
<synopsis> <synopsis>
int lo_truncate(PGcon *conn, int fd, size_t len); int lo_truncate(PGconn *conn, int fd, size_t len);
</synopsis> </synopsis>
This function truncates the large object This function truncates the large object
descriptor <parameter>fd</> to length <parameter>len</>. The descriptor <parameter>fd</> to length <parameter>len</>. The
@ -465,7 +465,7 @@ int lo_truncate(PGcon *conn, int fd, size_t len);
When dealing with large objects that might exceed 2GB in size, When dealing with large objects that might exceed 2GB in size,
instead use instead use
<synopsis> <synopsis>
int lo_truncate64(PGcon *conn, int fd, pg_int64 len); int lo_truncate64(PGconn *conn, int fd, pg_int64 len);
</synopsis> </synopsis>
This function has the same This function has the same
behavior as <function>lo_truncate</function>, but it can accept a behavior as <function>lo_truncate</function>, but it can accept a