Re: copy vs. C function - Mailing list pgsql-performance

From Tom Lane
Subject Re: copy vs. C function
Date
Msg-id 7080.1323876330@sss.pgh.pa.us
Whole thread Raw
In response to Re: copy vs. C function  (Jon Nelson <jnelson+pgsql@jamponi.net>)
Responses Re: copy vs. C function
List pgsql-performance
Jon Nelson <jnelson+pgsql@jamponi.net> writes:
> Regarding caching, I tried caching it across calls by making the
> TupleDesc static and only initializing it once.
> When I tried that, I got:

> ERROR:  number of columns (6769856) exceeds limit (1664)

> I tried to find some documentation or examples that cache the
> information, but couldn't find any.

You might find reading record_in to be helpful.  What it caches is not
exactly what you need to, I think, but it shows the general principles.
There are lots of other functions that use fn_extra to cache info, too.

            regards, tom lane

pgsql-performance by date:

Previous
From: idc danny
Date:
Subject: Re: copy vs. C function
Next
From: Jon Nelson
Date:
Subject: Re: copy vs. C function