pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Jackson, DeJuan <djackson@cpsgroup.com>
To: Bruce Momjian <maillist@candle.pha.pa.us>
To: Ansley, Michael <Michael.Ansley@intec.co.za>
Cc: 'pgsql-sql@postgresql.org' <pgsql-sql@postgreSQL.org>
Subject: RE: [SQL] Re: Good Optimization
Date: Fri, 9 Jul 1999 15:47:44 -0500
Message-ID: <D05EF808F2DFD211AE4A00105AA1B5D23212D1@cpsmail> (raw)
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > Hi, Bruce,
> >
> > I've only just picked up the thread on optimizations (I get the digest
> for
> > the pgsql-sql list). I really feel that a lot of effort could be saved
> with
> > some good benefits if a stored proc mechanism is put into place. Once
> that
> > has been done, it can be used to store temporary plans (procedures) for
> > ad-hoc queries which are released on the termination of the connection.
> > However, I think that a lot of users will develop stored procs to
> replace a
> > lot of their existing common SQL, in order to (partially) optimize their
> > systems. Perhaps in the PREPARE statement we could add a facility to
> allow
> > the user to specify the TTL of the cached proc for an ad-hoc query.
> >
> > When I talk about stored procs, I don't mean functions. We already have
> > those. I mean procedures that are able to return a rowset. Just to
> make
> > sure nobody gets the wrong idea.
>
> Not sure why our functions can't return tuples.
>
> > Also, has anything happened about the idea to get PG to cluster
> (somebody
> > mentioned Beowulf)?
>
> No one has mentioned this.
>
I believe he's referring to having PostgreSQL have distributed
loading across multiple machines. I've been thinking of testing a Beowulf
setup here for fault tolerance and fail-over. It's might be the most
elegant and easy solution to implement, starting with a Red Hat box.
It's time to move www.airforce.com to PostgreSQL and PHP :)
-DEJ
view thread (27+ messages) latest in thread
Message-ID: <D05EF808F2DFD211AE4A00105AA1B5D23212D1@cpsmail> Permalink: ../D05EF808F2DFD211AE4A00105AA1B5D23212D1@cpsmail/ Also on: postgresql.org/message-id/D05EF808F2DFD211AE4A00105AA1B5D23212D1@cpsmail ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-sql@postgresql.org Cc: djackson@cpsgroup.com, maillist@candle.pha.pa.us, Michael.Ansley@intec.co.za Subject: Re: [SQL] Re: Good Optimization In-Reply-To: <D05EF808F2DFD211AE4A00105AA1B5D23212D1@cpsmail> References: <D05EF808F2DFD211AE4A00105AA1B5D23212D1@cpsmail> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox