pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gerald Gutierrez <pozix@home.com>
To: David Olbersen <dave@slickness.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: Temp Tables & Connection Pooling
Date: Sat, 03 Mar 2001 07:43:24 -0800
Message-ID: <5.0.2.1.0.20010303073950.02a1a388@mail.rchmd1.bc.wave.home.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0103021247290.18710-100000@bubbles.electricu topia.net>
References: <5.0.2.1.0.20010302103136.02a1a388@mail.rchmd1.bc.wave.home.com>

At 12:48 PM 3/2/2001 -0800, David Olbersen wrote:
>On Fri, 2 Mar 2001, Gerald Gutierrez wrote:
>
>->Recently I wanted to implement Dijkstra's algorithm as a stored procedure,
>->and finding that PL/PGSQL cannot return record sets, I thought about using
>->a temporary table for the results. If tempoary tables are session-specific,
>->however, then wouldn't connection pooling make it unusable since the table
>->might "disappear" from one query to the next? What are alternative
>->approaches to implementing Dijkstra's algorithm inside the database?
>
><newbie>
>Wouldn't a VIEW do what you want?
></newbie>

No it wouldn't. Executing Dijkstra would involve executing iterative logic 
on multiple tables and storing intermediate results in a form that can be 
returned to the user but does not affect the actual persistent table schema 
(e.g. a record set, or a temporary table). A view is used to provide a 
simplified or alternative way of looking at a set of data, and cannot 
cannot generally multi-step operation that data prior to returning to the user.





view thread (5+ messages)  latest in thread

Message-ID: <5.0.2.1.0.20010303073950.02a1a388@mail.rchmd1.bc.wave.home.com>
Permalink:  ../5.0.2.1.0.20010303073950.02a1a388@mail.rchmd1.bc.wave.home.com/
Also on:    postgresql.org/message-id/5.0.2.1.0.20010303073950.02a1a388@mail.rchmd1.bc.wave.home.com

 · 

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: pozix@home.com, dave@slickness.org
  Subject: Re: Temp Tables & Connection Pooling
  In-Reply-To: <5.0.2.1.0.20010303073950.02a1a388@mail.rchmd1.bc.wave.home.com>
  References: <5.0.2.1.0.20010302103136.02a1a388@mail.rchmd1.bc.wave.home.com> <5.0.2.1.0.20010303073950.02a1a388@mail.rchmd1.bc.wave.home.com>

* 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