2012/11/25 Bexley Hall :
> Hi Pavel,
>
> On 11/24/2012 9:47 PM, Pavel Stehule wrote:
>>
>> Hello
>>
>> you can try use plperl as cache
>>
>>
>> http://okbob.blogspot.cz/2007/12/using-shared-as-table-cache-in-plperl.html
>
>
> But how is this any different than just creating a named/shared
> table m
Hi Kevin,
On 11/25/2012 8:10 AM, Kevin Grittner wrote:
Bexley Hall wrote:
Specifically, I have several computationally expensive
functions that derive their results from specific values of
these base types. *Solely*. (For example, area() when
applied to a given "circle" always yields the same
Hi Pavel,
On 11/24/2012 9:47 PM, Pavel Stehule wrote:
Hello
you can try use plperl as cache
http://okbob.blogspot.cz/2007/12/using-shared-as-table-cache-in-plperl.html
But how is this any different than just creating a named/shared
table manually?
And, how do further/additional accesses (by
Bexley Hall wrote:
> Specifically, I have several computationally expensive
> functions that derive their results from specific values of
> these base types. *Solely*. (For example, area() when
> applied to a given "circle" always yields the same result...
> though this is a trivial/inexpensive fu
Hello
you can try use plperl as cache
http://okbob.blogspot.cz/2007/12/using-shared-as-table-cache-in-plperl.html
Regards
Pavel Stehule
2012/11/25 Bexley Hall :
> Hi,
>
> In the absence of query caching AND NOT WANTING TO FORCE
> THE APPLICATION TO DO SO EXPLICITLY, I'm looking for ideas
> as
Frank Joerdens wrote:
>
> On Wed, Nov 01, 2000 at 10:16:58AM +, Poul L. Christiansen wrote:
> > PostgreSQL hits the disk on UPDATE/DELETE/INSERT operations. SELECT's
> > are cached, but the default cache is only ½MB of RAM. You can change
> > this to whatever you want.
>
> That sound like a
On Wed, Nov 01, 2000 at 10:16:58AM +, Poul L. Christiansen wrote:
> PostgreSQL hits the disk on UPDATE/DELETE/INSERT operations. SELECT's
> are cached, but the default cache is only ½MB of RAM. You can change
> this to whatever you want.
That sound like a very cool thing to do, and the defaul
> PostgreSQL hits the disk on UPDATE/DELETE/INSERT operations. SELECT's
> are cached, but the default cache is only ½MB of RAM. You can change
> this to whatever you want.
>
> I'm using Cold Fusion and it can cache queries itself, so no database
> action is necessary. But I don't think PHP and oth
Daniel Freedman wrote:
>
> On the topic of query cache (or maybe this is just tangential and I'm
> confused):
>
> I've always heard that Oracle has the ability to essentially suck in as
> much of the database into RAM as you have memory to allow it, and can then
> just run its queries on that in
