Re: Server side lo-funcs name

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Server side lo-funcs name
Date: 2013-06-11 12:07:46
Message-ID: CA+TgmoYnL4RV1qR28NHuNLR6wmC_YMsU+PZ5YmQUjvON-MgHsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 11, 2013 at 1:32 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> Recently we got a complain about server side large object function
>> names described in the doc:
>> http://www.postgresql.org/message-id/51B2413F.8010305@gmail.com
>>
>> In the doc:
>> http://www.postgresql.org/docs/9.3/static/lo-funcs.html
>>
>> "There are server-side functions callable from SQL that correspond to
>> each of the client-side functions described above; indeed, for the
>> most part the client-side functions are simply interfaces to the
>> equivalent server-side functions"
>>
>>>From the description it is hard for users to find out server side
>> functions "loread" and "lowrite" becuase they are looking for
>> "lo_read" and "lo_write". So I think his complain is fair. Included
>> patches attempt to fix the problem.
>
> I have committed this.

Did you see my email with proposed alternative text? You didn't even
fix the whitespace error I pointed out.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2013-06-11 12:41:10 Re: JSON and unicode surrogate pairs
Previous Message Stephen Frost 2013-06-11 11:26:47 Re: erroneous restore into pg_catalog schema