From: Aaron Birkland <birkie@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Array types and loading
Date: Wed, 18 Aug 2004 17:47:50 -0400
Message-ID: <19ab0ccd04081814473ca44daf@mail.gmail.com> (raw)
In-Reply-To: <4152.1092865161@sss.pgh.pa.us>
References: <19ab0ccd040818123936c1cdd3@mail.gmail.com>
<4152.1092865161@sss.pgh.pa.us>
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@sss.pgh.pa.us> wrote:
> Aaron Birkland <birkie@gmail.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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: birkie@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Array types and loading
In-Reply-To: <19ab0ccd04081814473ca44daf@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox