Re: carray_to_bytea? - Mailing list pgsql-general

From Tom Lane
Subject Re: carray_to_bytea?
Date
Msg-id 48898.1445530353@sss.pgh.pa.us
Whole thread Raw
In response to carray_to_bytea?  (Ken Been <kbbeen@gmail.com>)
Responses Re: carray_to_bytea?  (Ken Been <kbbeen@gmail.com>)
List pgsql-general
Ken Been <kbbeen@gmail.com> writes:
> I'd like to propose a carray_to_bytea function, similar to
> cstring_to_text_with_len, declared in src/include/utils.h and implemented
> in src/backend/utils/adt/varlena.c.  The implementation would be the same
> as cstring_to_text_with_len, but with a different return type.

> I have put the implementation in my code, but I'd much prefer to use a
> public API with hidden implementation.

Hardly worth it, really.  There is nothing to a bytea except the length
and the bytes, so I'd say that any "information hiding" you might be
getting is illusory.  Moreover, such a function would encourage people
to assemble useless intermediate copies of the bytestring rather than
constructing it directly in the result object.  Consider for example what
byteacat() would look like if it were required to use such a function.

(To some extent these arguments could also be made to apply to
cstring_to_text_with_len, of course, but I consider that to be a sibling
of cstring_to_text, which does have considerable usefulness.)

            regards, tom lane


pgsql-general by date:

Previous
From: bricklen
Date:
Subject: Re: ERROR: invalid page in block 1226710 of relation base/16750/27244
Next
From: Tom Lane
Date:
Subject: Re: ERROR: invalid page in block 1226710 of relation base/16750/27244