From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "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-18 21:21:30 |
Message-ID: | C041B9DA.1F77C%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom,
On 3/17/06 9:59 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This would buy what exactly?
I guess you didn't read the other 80% of the post.
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.
- Luke
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2006-03-18 21:29:37 | Re: Automatically setting work_mem |
Previous Message | Josh Berkus | 2006-03-18 18:36:09 | Re: PostgreSQL Anniversary Proposals -- Important |
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2006-03-18 21:29:37 | Re: Automatically setting work_mem |
Previous Message | Luke Lonergan | 2006-03-18 08:05:19 | Re: Automatically setting work_mem |