diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-06-12 15:39:09 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-06-12 15:39:09 -0400 |
| commit | 154146d208de7518bb6c8131dc8d2361f7f36f56 (patch) | |
| tree | 0ac40e6ac000ea4f31bde8ad8d8f781a5e1aaab2 /src/include/libpq | |
| parent | 7937910781a823382b3f76b4b811791804431927 (diff) | |
| download | postgresql-154146d208de7518bb6c8131dc8d2361f7f36f56.tar.gz | |
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 'src/include/libpq')
| -rw-r--r-- | src/include/libpq/be-fsstubs.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/include/libpq/be-fsstubs.h b/src/include/libpq/be-fsstubs.h index 84ee49690c..b6c8f7f8cb 100644 --- a/src/include/libpq/be-fsstubs.h +++ b/src/include/libpq/be-fsstubs.h @@ -25,7 +25,7 @@ extern Datum lo_export(PG_FUNCTION_ARGS); extern Datum lo_creat(PG_FUNCTION_ARGS); extern Datum lo_create(PG_FUNCTION_ARGS); -extern Datum lo_create_bytea(PG_FUNCTION_ARGS); +extern Datum lo_from_bytea(PG_FUNCTION_ARGS); extern Datum lo_open(PG_FUNCTION_ARGS); extern Datum lo_close(PG_FUNCTION_ARGS); |
