pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jan Wieck <janwieck@yahoo.com>
Cc: Murray Prior Hobbs <murray@efone.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: temporary tables, plpgsql and yes i bet this has been asked
Date: Mon, 4 Feb 2002 15:43:15 -0500 (EST)
Message-ID: <200202042043.g14KhFl10735@candle.pha.pa.us> (raw)
In-Reply-To: <12068.1012855160@sss.pgh.pa.us>

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Temp tables are the wrong way to think about it.  *Any* invalidation
> >> of schema data referred to in a query plan should cause replanning.
> >> We have a TODO item covering this already, don't we?
> 
> > If we do, I don't see it.  Care to give me one?
> 
> Hmm, I don't see one either.  Odd, we've sure discussed it often enough.
> How about
> 
> * Flush cached query plans when their underlying catalog data changes

Yes, under DEPENDENCIE CHECKING.  Done.

> Probably belongs under "DEPENDENCY CHECKING".
> 
> 
> BTW, I was slightly startled to read this under URGENT:
> 
> * Allow row re-use without vacuum (Tom)
> 
> I don't consider this urgent or even likely ever to happen, and
> I certainly have not taken responsibility to do it.

Well, a name doesn't mean someone claimed it but rather the _expert_ on
the item.  I added this item assuming it was going to be accomplished
with some type of auto-vacuum.  I will clearify it to mention
auto-vacuum, if that is OK.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (12+ messages)  latest in thread

Message-ID: <200202042043.g14KhFl10735@candle.pha.pa.us>
Permalink:  ../200202042043.g14KhFl10735@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200202042043.g14KhFl10735@candle.pha.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, janwieck@yahoo.com, murray@efone.com
  Subject: Re: temporary tables, plpgsql and yes i bet this has been asked
  In-Reply-To: <200202042043.g14KhFl10735@candle.pha.pa.us>

* 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