Re: proposal: lob conversion functionality - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: lob conversion functionality
Date
Msg-id CAFj8pRCp1NR-FW=55BZ7GLGWrH+2tobCGGou5g8XmpqiQbnkJw@mail.gmail.com
Whole thread Raw
In response to Re: proposal: lob conversion functionality  (Noah Misch <noah@leadboat.com>)
Responses Re: proposal: lob conversion functionality  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
Hello

here is patch

Regards

Pavel


2013/10/21 Noah Misch <noah@leadboat.com>
On Mon, Oct 21, 2013 at 08:10:24PM +0200, Pavel Stehule wrote:
> > On 10/20/2013 07:52 PM, Noah Misch wrote:
> >> Anything we do here effectively provides wrappers around the existing
> >> functions tailored toward the needs of libpq.

To clarify the above statement: the existing lo* SQL functions are designed to
fit the needs of the libpq APIs that call those SQL functions internally.  The
additions we're discussing are SQL functions designed to fit the needs of
user-written SQL statements.

> I am for including to core - we have no buildin SQL functions that allows
> access simple and fast access on binary level. Next - these functions
> completes lo functionality.
>
> Other questions - should be these functions propagated to libpq?

No; I agree that the existing libpq large object API is adequate.

> and who will write patch? You or me?

If you're prepared to change the function names and add the subset-oriented
functions, I would appreciate that.

Thanks,
nm

--
Noah Misch
EnterpriseDB                                 http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Gavin Flower
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement