Re: feature request - datum_compute_size and datum write_should be public - Mailing list pgsql-hackers

From Tom Lane
Subject Re: feature request - datum_compute_size and datum write_should be public
Date
Msg-id 29098.1328077783@sss.pgh.pa.us
Whole thread Raw
In response to feature request - datum_compute_size and datum write_should be public  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: feature request - datum_compute_size and datum write_should be public  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: feature request - datum_compute_size and datum write_should be public
Next
From: Pavel Stehule
Date:
Subject: Re: feature request - datum_compute_size and datum write_should be public