Skip site navigation (1) Skip section navigation (2)

Re: Inlining comparators as a performance optimisation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pierre C <lists(at)peufeu(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>,Peter Geoghegan <peter(at)2ndquadrant(dot)com>,PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inlining comparators as a performance optimisation
Date: 2012-01-28 14:55:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Jan 13, 2012 at 10:48:56AM +0100, Pierre C wrote:
> Maybe an extra column in pg_proc would do (but then, the proargtypes
> and friends would describe only the sql-callable version) ?
> Or an extra table ? pg_cproc ?
> Or an in-memory hash : hashtable[ fmgr-callable function ] => C version
> - What happens if a C function has no SQL-callable equivalent ?
> Or (ugly) introduce an extra per-type function
> type_get_function_ptr( function_kind ) which returns the requested
> function ptr
> If one of those happens, I'll dust off my old copy-optimization patch ;)

I agree that COPY is ripe for optimization, and I am excited you have
some ideas on this.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + It's impossible for everything to be true. +

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2012-01-28 15:31:57
Subject: Re: initdb and fsync
Previous:From: Simon RiggsDate: 2012-01-28 13:57:58
Subject: Re: Avoiding shutdown checkpoint at failover

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group