Marc Munro <[EMAIL PROTECTED]> writes:
> On Thu, 2008-06-12 at 19:10 -0400, Tom Lane wrote:
>> It'd only last until the next time Bruce runs his script that
>> static-izes things that aren't used outside their own module ...
> Hmmm. Does that script look in contrib? If so I'd be happy to provide
On Thu, 2008-06-12 at 19:10 -0400, Tom Lane wrote:
> Marc Munro <[EMAIL PROTECTED]> writes:
> > So, would there be any chance of redefining the base64 functions in
> > encode.c as extern to eliminate this redundancy?
>
> It'd only last until the next time Bruce runs his script that
> static-izes t
On Thu, 2008-06-12 at 19:07 -0400, Andrew Dunstan wrote:
> Marc Munro wrote:
> > I require base64 or some similar encoding scheme from a C language. . .
> >
> > I know I could call these functions indirectly by calling binary_ecncode
> > through DirectFunctionCalln() but this is a whole lot more co
Marc Munro <[EMAIL PROTECTED]> writes:
> So, would there be any chance of redefining the base64 functions in
> encode.c as extern to eliminate this redundancy?
It'd only last until the next time Bruce runs his script that
static-izes things that aren't used outside their own module ...
Marc Munro wrote:
I require base64 or some similar encoding scheme from a C language
extension and need it to be as fast as reasonably possible. In
src/backend/utils/adt/encode.c there are functions b64_encode and
b64_decode which would be ideal but these are defined static and so are
not av
