Re: Non-standard feature request - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: Non-standard feature request
Date
Msg-id Pine.LNX.4.21.0206280216180.26102-101000@linuxworld.com.au
Whole thread Raw
In response to Re: Non-standard feature request  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: Non-standard feature request
Re: Non-standard feature request
Re: Non-standard feature request
List pgsql-hackers
Slight bug in the previous patch. Logically (and according to SQL99's
treatment of ON COMMIT), it can be specified only for CREATE TEMP
TABLE. The patch throws an error if only CREATE TABLE has been specified.

Gavin

On Fri, 28 Jun 2002, Gavin Sherry wrote:

> On Fri, 14 Jun 2002, Gavin Sherry wrote:
>
> > On Thu, 13 Jun 2002, Mike Mascari wrote:
> >
> > >
> > > CREATE TEMPORARY TABLE
> > > ...
> > > ON COMMIT DROP;
> > >
> > > pseudo-compatible with the SQL-standard of:
> > >
> > > ON COMMIT { DELETE | PRESERVE } ROWS;
> > >
> > > so one day PostgreSQL's grammar would look like:
> > >
> > > ...
> > > ON COMMIT { DROP | { DELETE | PRESERVE } ROWS };
> >
> > I think this is a pretty useful feature. Shouldn't require too much
> > work. A new relkind or a bool in TempTable and a little code in
> > AtEOXact_temp_relations() to heap_drop_with_catalog() the registered temp
> > table.
> >
> > Anyone else keen for this feature?
>
> Attached is a patch implementing this. The patch is against 7.2.1
> source. The grammar introduced is of the form:
>
>     CREATE TEMP TABLE ... ON COMMIT DROP;
>
> Is this a desirable feature? Seems pretty useful to me.
>
> Gavin
>
>

pgsql-hackers by date:

Previous
From: "Josh Berkus"
Date:
Subject: Re: Support (was: Democracy and organisation)
Next
From: Mike Mascari
Date:
Subject: Re: Non-standard feature request