[PERFORM] Slow C Function

Hi, We've got a C function that we use here and we find that for every connection, the first run of the function is much slower than any subsequent runs. ( 50ms compared to 8ms) Besides using connection pooling, are there any options to improve performance? By the way, we are using pg version

[PERFORM] Dynamically loaded C function performance

Hi, We've got a C function that we use here and we find that for every connection, the first run of the function is much slower than any subsequent runs. ( 50ms compared to 8ms) Besides using connection pooling, are there any options to improve performance? -Adam

[PERFORM]

Hi, We've got a C function that we use here and we find that for every connection, the first run of the function is much slower than any subsequent runs. ( 50ms compared to 8ms) Besides using connection pooling, are there any options to improve performance? By the way, we are using pg version

Re: [PERFORM] Building postmaster with Profiling Support WAS Tweaking a C

- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Palmblad Sent: Wednesday, April 06, 2005 7:23 PM To: pgsql-performance@postgresql.org Subject: [PERFORM] Tweaking a C Function I wrote I wanted to see if I could squeeze any more performance out of a C set returning function I

[PERFORM] Tweaking a C Function I wrote

I wanted to see if I could squeeze any more performance out of a C set returning function I wrote. As such, I looked to a profiler. Is it possible to get profile information on the function I wrote? I've got postmaster and my function compiled with profiling support, and can find the

[PERFORM] Bad Index Choices with user defined data type

I've got a table using a data type that I have created as the type for its primary key. I (hope) I have the type set up properly - it seems okay, and does not have any problem creating a b-tree index for the type. The problem I am having is that the index seems to never be chosen for use. I