Re: Automatically setting work_mem

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Luke Lonergan <llonergan(at)greenplum(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Automatically setting work_mem
Date: 2006-03-21 22:18:40
Message-ID: 1142979520.24487.534.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sat, 2006-03-18 at 13:21 -0800, Luke Lonergan wrote:

> In short, faster performance through more aggressive runtime compilation. A
> JIT for the database kernel. It's not like I'm on shaky ground here - other
> commercial DBMS have done it for over a decade.

I think what Luke may be referring to is the ability to compile WHERE
clauses to remove the bottleneck around Eval for complex searches.

Best Regards, Simon Riggs

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-03-21 22:23:59 Re: [GENERAL] A real currency type
Previous Message Martijn van Oosterhout 2006-03-21 22:12:12 Re: [GENERAL] A real currency type

Browse pgsql-patches by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-03-21 22:28:23 Re: Automatically setting work_mem
Previous Message Simon Riggs 2006-03-21 20:33:50 Re: WAL logging of SELECT ... INTO command