From: Riccardo G. Facchini <abief_ag_-postgresql@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: Re: CREATE TEMPORARY TABLE .. ON COMMIT DROP question
Date: Fri, 19 Nov 2004 07:54:50 -0800 (PST)
Message-ID: <20041119155450.21057.qmail@web13903.mail.yahoo.com> (raw)
In-Reply-To: <27902.1100876895@sss.pgh.pa.us>
--- Tom Lane <__> wrote:
> "Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com> writes:
> > I'm trying to understand where the "[ ON COMMIT { PRESERVE ROWS |
> > DELETE ROWS | DROP } ]" is stored when defining a temporary table.
>
> I don't believe it's stored anyplace visible :-(. There's some
> private
> state in the memory of the backend that owns the table. Look into
> commands/tablecmds.c.
>
> regards, tom lane
>
[..]
Thanks, I'm reading the code at this right moment.
I'm wandering if this is consistent... I mean, a temporary table finds
its way to the pg_class as any other table, so I'm able to retrieve a
lot of things regarding that particular table. Even if a temporary
table is something that's assumed to be built by my own session, I may
want to know if what I store there is eventually destroyed.
this would mean extending the pg_class definition and generating the
associated code... not a big job, but something that may not be done
lightly.
I'm writing a set of utilities that run on pure plpgsql that provide
info about the objects contained in the database, and I started with
one of those things that are not provided by the pg_xxx functions, the
table. My code is capable of rendering the code of a temporary table,
but not capturing the info regarding the "ON COMMIT" part...
regards,
R.
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: abief_ag_-postgresql@yahoo.com
Subject: Re: CREATE TEMPORARY TABLE .. ON COMMIT DROP question
In-Reply-To: <20041119155450.21057.qmail@web13903.mail.yahoo.com>
* 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