| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:20:53 |
| Message-ID: | 1029252054.74400.50.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2002-08-13 at 11:11, 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.
I was playing with this a while back (when I had initially added CASCADE
to tables). I believe that in the event of a crash the temp tables are
not removed until their next use. This means that stale *real* items
may litter the system but the temp table no longer exists in these rare
occurrences.
However, having all temporary items removed during backend startup would
remove this case.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-08-13 15:22:47 | Re: Temporary Views |
| Previous Message | Helge Bahmann | 2002-08-13 15:19:31 | Re: [HACKERS] Linux Largefile Support In Postgresql RPMS |