aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-06-12 15:39:09 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-06-12 15:39:09 -0400
commit154146d208de7518bb6c8131dc8d2361f7f36f56 (patch)
tree0ac40e6ac000ea4f31bde8ad8d8f781a5e1aaab2 /doc/src
parent7937910781a823382b3f76b4b811791804431927 (diff)
downloadpostgresql-154146d208de7518bb6c8131dc8d2361f7f36f56.tar.gz
postgresql-154146d208de7518bb6c8131dc8d2361f7f36f56.zip
Rename lo_create(oid, bytea) to lo_from_bytea().
The previous naming broke the query that libpq's lo_initialize() uses to collect the OIDs of the server-side functions it requires, because that query effectively assumes that there is only one function named lo_create in the pg_catalog schema (and likewise only one lo_open, etc). While we should certainly make libpq more robust about this, the naive query will remain in use in the field for the foreseeable future, so it seems the only workable choice is to use a different name for the new function. lo_from_bytea() won a small straw poll. Back-patch into 9.4 where the new function was introduced.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/lobj.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
index d403586a054..c0174b71bee 100644
--- a/doc/src/sgml/lobj.sgml
+++ b/doc/src/sgml/lobj.sgml
@@ -547,16 +547,16 @@ int lo_unlink(PGconn *conn, Oid lobjId);
<row>
<entry>
<indexterm>
- <primary>lo_create</primary>
+ <primary>lo_from_bytea</primary>
</indexterm>
- <literal><function>lo_create(<parameter>loid</parameter> <type>oid</type>, <parameter>string</parameter> <type>bytea</type>)</function></literal>
+ <literal><function>lo_from_bytea(<parameter>loid</parameter> <type>oid</type>, <parameter>string</parameter> <type>bytea</type>)</function></literal>
</entry>
<entry><type>oid</type></entry>
<entry>
Create a large object and store data there, returning its OID.
Pass <literal>0</> to have the system choose an OID.
</entry>
- <entry><literal>lo_create(0, E'\\xffffff00')</literal></entry>
+ <entry><literal>lo_from_bytea(0, E'\\xffffff00')</literal></entry>
<entry><literal>24528</literal></entry>
</row>