From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | Perez <arturo(at)ethicist(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Cached Query Plans (was: global prepared statements) |
Date: | 2008-04-13 01:39:04 |
Message-ID: | 36e682920804121839x3644dca8h1495ee43faeba923@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Apr 12, 2008 at 8:44 AM, Perez <arturo(at)ethicist(dot)net> wrote:
> Doesn't Oracle do this now transparently to clients?
Of course it does, and it has since the late 80's I believe.
> Oracle keeps a statement/plan cache in its shared memory segment (SGA)
> that greatly improves its performance at running queries that don't
> change very often.
Yep.
> From that point of view, Oracle at least sees benefits in doing this.
Yes, it is also a bit more advanced than we're discussing here, so
I'll just leave it as.
> From my POV a transparent performance enhancer for all those PHP and
> Rails apps out there.
Yes.
>
> With plan invalidation in 8.3 this becomes feasible for pgSQL to do as
> well.
>
> -arturo
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2008-04-13 01:42:05 | Re: Cached Query Plans (was: global prepared statements) |
Previous Message | Jonah H. Harris | 2008-04-13 01:38:59 | Re: Cached Query Plans (was: global prepared statements) |