From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Mattias Kregert <mattias(at)kregert(dot)se>, TANIDA Yutaka <tanida(at)sra(dot)co(dot)jp>, Boris Popov <boris(at)procedium(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Temp rows - is it possible? |
Date: | 2003-11-10 19:08:47 |
Message-ID: | 200311101908.hAAJ8l424418@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> We recently decided we had to forbid foreign-key references from temp
> >> tables to permanent tables because of this effect. I wonder whether
> >> we won't end up forbidding temp tables as children of permanent tables
> >> too.
>
> > Yep, I think we will have to do that. TODO item?
>
> Plan B would be to arrange for the planner to ignore temp tables of
> other backends whenever it is searching for child tables. Then the
> behavior would be predictable: you never see any rows inserted in other
> people's temp child tables (and cannot update or delete 'em, either).
> I'm not sure if this is the behavior the OP wanted, but it seems at
> least marginally useful.
Agreed. It seems wrong that a session should ever see other people's
temp tables as children.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Jack Orenstein | 2003-11-10 19:12:19 | Why does primary key violation cause an abort? |
Previous Message | Mark Harrison | 2003-11-10 19:06:04 | Re: why does explain tell me I'm using a seq scan? |