From: | Aaron Birkland <birkie(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Array types and loading |
Date: | 2004-08-18 21:47:50 |
Message-ID: | 19ab0ccd04081814473ca44daf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
You got it.. 7.3 (should have mentioned that). We're planning to
upgrade to 8.0 anyway in the future, so it's good to know. Thanks!
-Aaron
On Wed, 18 Aug 2004 17:39:21 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Aaron Birkland <birkie(at)gmail(dot)com> writes:
> > In a nutshell, it looks like whenever COPY is invoked, and when a user
> > defined type is used in an array, then stat64() will be called for
> > each row accessed on the shared library relevant for the user defined
> > type.
>
> Let me guess ... PG 7.3 or older?
>
> 7.4 should avoid the problem because array_in() caches function lookup
> information for the element type's input function across multiple calls.
>
> In 8.0 there's also a cache at the fmgr_info() level to eliminate
> repeated searches for a dynamically loaded function.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | DeJuan Jackson | 2004-08-18 23:02:08 | Re: Why is the number of dead tuples causing the performance |
Previous Message | Tom Lane | 2004-08-18 21:39:21 | Re: Array types and loading |