2012/2/1 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> I looked to sources and I found a some useful routines for people who
>> write extensions and probably PL too.
>
>> There are datum_compute_size and datum_write from range_types.c. These
>> routines can be used in PL libs and maybe in other places.
>
>> Should be these routines moved to varlena.c and be public?
>
> Why?  It is not common for types to contain other types, and it
> certainly isn't likely to happen without needing lots of other
> infrastructure --- the existing examples are arrays, records, and
> rangetypes, and all of those come with lots of baggage.  And there
> are a number of choices in those functions that are pretty specific to
> rangetypes, as illustrated by the fact that they're not already sharing
> code with either arrays or records.

For example I can use this code in my implementation of set of enum
(enumset datatype) because I have to wrap a array sometimes (I reuse a
array infrastructure).

In orafce I can use this code for serialisation and deserialisation
Datums - it is used more times there

Pavel

>
>                        regards, tom lane

In response to

• Re: feature request - datum_compute_size and datum write_should be public at 2012-02-01 06:29:43 from Tom Lane

Responses

• Re: feature request - datum_compute_size and datum write_should be public at 2012-02-01 23:47:05 from Jim Nasby

pgsql-hackers by date

Next:	From: Kyotaro HORIGUCHI	Date: 2012-02-01 08:32:16
	Subject: Re: Speed dblink using alternate libpq tuple storage
Previous:	From: Tom Lane	Date: 2012-02-01 06:29:43
	Subject: Re: feature request - datum_compute_size and datum write_should be public