From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Simplifying identification of temporary tables |
Date: | 2005-07-14 20:12:35 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3415C2DA8@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> That would respond to the abstraction concern in a more complete
> fashion. I thought about that one too, but felt that the ability to
> look at the whole pg_class row (and not only check existence) had some
> value. Also, I've seen people doing things like
> ... where relname LIKE 'pattern' and ...
> which still works with the namespace OID function but would not work
> with a does_temp_table_exist() function. I wouldn't object to doing
> both this and the OID function, though. Do you have a proposal for
> the exact spelling of the exists() function?
I guess pg_temp_table_exists(text) is the most straightforward.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-07-14 20:29:34 | Re: [Bizgres-general] A Guide to Constraint Exclusion |
Previous Message | David Fetter | 2005-07-14 20:09:16 | Re: Toward pg_upgrade |