| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Temporary Views |
| Date: | 2002-08-13 15:22:47 |
| Message-ID: | 1029252168.74400.53.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2002-08-13 at 11:18, Bruce Momjian wrote:
> Tom Lane wrote:
> > Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> > > I'm thinking that temporary views should be pretty trivial to
> > > implement.
> >
> > ... except not so trivial, per the rest of your note.
> >
> > Do we actually need any such feature? Views on temp tables already work
> > correctly in CVS tip: the implicit DROP CASCADE on temp tables at
> > backend exit makes such views go 'way too.
>
> Oh. but RESTRICT is the default. Seems like the view should go away no
> matter what, and if they mix temp and non-temp tables, is it obvious
> that the view will disappear if they didn't specify TEMP on view
> creation.
When the backend exits the code that removes temp tables is CASCADE by
default and anything depending on it will disappear.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-13 15:24:38 | Re: db partial dumping with pg_dump |
| Previous Message | Rod Taylor | 2002-08-13 15:20:53 | Re: Temporary Views |