From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: C function accepting/returning cstring vs. text |
Date: | 2010-01-27 15:53:11 |
Message-ID: | 20100127155311.GC3559@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ivan Sergio Borgonovo wrote:
> On Wed, 27 Jan 2010 11:49:46 -0300
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> > > There are a lot of functions in contrib taking cstring input and
> > > returning cstring output.
> > > Are they just in the same "special" class of [type]in, [type]out
> > > [type]recv... functions?
>
> > Probably, but I didn't check.
>
> Does this nearly translate to:
> "nothing you should care about right now and anyway just functions
> that won't return results to SQL"?
I meant "they are almost certainly in the same class as typein and
typeout, but I didn't check every single one of them".
As far as I can tell you are not writing an output function, but
rather a debugging function of sorts. I see no reason to return cstring.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-01-27 15:58:17 | Re: Review: listagg aggregate |
Previous Message | Hitoshi Harada | 2010-01-27 15:43:05 | Re: Review: Typed Table |