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

Re: Re: [GENERAL] Query caching

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Alfred Perlstein <bright(at)wintelcom(dot)net>
Cc: Steve Wolfe <steve(at)iboats(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [GENERAL] Query caching
Date: 2000-11-01 02:01:16
Message-ID: Pine.BSF.4.21.0010312159400.494-100000@thelab.hub.org (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
On Tue, 31 Oct 2000, Alfred Perlstein wrote:

> * Steve Wolfe <steve(at)iboats(dot)com> [001031 13:47] wrote:
> > 
> > > >    (Incidentally,  we've toyed  around with  developping a
> > query-caching
> > > > system that would sit betwen PostgreSQL and our DB libraries.
> > >
> > >  Sounds  amazing, but  requires some  research, I  guess. However,  in
> > many
> > > cases one  would be  more than  happy with  cahced connections.  Of
> > course,
> > > cahced query results  can be naturally added to that,  but just
> > connections
> > > are OK to start with. Security....
> > 
> >     To me, it doesn't sound like it would be that difficult of a project, at
> > least not for the likes of the PostgreSQL developpers.  It also doesn't seem
> > like it would really introduce any security problems, not if it were done
> > inside of PostgreSQL.  Long ago, I got sidetracked from my endeavors in C,
> > and so I don't feel that I'm qualified to do it.  (otherwise, I would have
> > done it already. : ) )   If you wanted it done in Perl or Object Pascal, I
> > could help. : )
> > 
> >     Here's a simple design that I was tossing back and forth.  Please
> > understand that I'm not saying this is the best way to do it, or even a good
> > way to do it.  Just a possible way to do it.  I haven't been able to give it
> > as much thought as I would like to.  Here goes.
> > 
> > ------------
> > Implementation
> > 
> 
> [snip]
> 
> Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> Implemented stored proceedures for
> postgresql but still hasn't been approached to integrated them.

someone has to approach him to integrate them? *raised eyebrow*

Karel, where did things stand the last time this was brought up?  We
haven't gone beta yet, can you re-submit a patch for v7.1 before beta so
that we can integrate the changes?  *Maybe*, if possible, submit it such
that its a compile time option, so that its there if someone like Alfred
wants to be brave, but it won't zap everyone if there is a bug?


In response to

Responses

pgsql-hackers by date

Next:From: Bruce HartzlerDate: 2000-11-01 02:07:53
Subject: Re: add darwin/osxpb support to cvs
Previous:From: Alex PilosovDate: 2000-11-01 01:24:56
Subject: Re: how good is PostgreSQL

pgsql-general by date

Next:From: KMillerDate: 2000-11-01 02:08:18
Subject: date question?
Previous:From: Alex PilosovDate: 2000-11-01 01:24:56
Subject: Re: how good is PostgreSQL

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