Seems worthwhile to me --- any objections? Any better ideas about a
name?
pg_session_temp_namespace()
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining col
> 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 'patte
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> That said, I think what you are proposing is good since it causes less
> log pollution. Although I would prefer to return the name of the
> namespace, not the oid,
I thought about that, but it pushes you right back to having to do a
join with pg_name
Tom Lane wrote:
> Currently, the recommended way to ask "have I already created a temp
> table named foo" is something like
>
> select * from pg_class
> where relname = 'foo' and pg_table_is_visible(oid);
>
> If there's a possibility that a regular table named 'foo' exists,
> then thi
Currently, the recommended way to ask "have I already created a temp
table named foo" is something like
select * from pg_class
where relname = 'foo' and pg_table_is_visible(oid);
If there's a possibility that a regular table named 'foo' exists,
then this isn't good enough and you
