[BUGS] BUG #5943: jdbc client doesn't omit pg_toast_temp tables from schema views

[Daniel Ceregatti]

The following bug has been logged online:

Bug reference:  5943
Logged by:  Daniel Ceregatti
Email address:  dan...@ceregatti.org
PostgreSQL version: N/A
Operating system:   N/A
Description:jdbc client doesn't omit pg_toast_temp tables from
schema views
Details: 

In the file org/postgresql/jdbc2/AbstractJdbc2DatabaseMetaData.java is the
query:

sql = "SELECT nspname AS TABLE_SCHEM FROM pg_catalog.pg_namespace WHERE
nspname <> 'pg_toast' AND nspname !~ '^pg_temp_' ORDER BY TABLE_SCHEM";

Using Data Tools Platform in eclipse I was able to see all the
pg_toast_temp_XXX schemas in the schema view.

Using postgresql-9.0-801.jdbc4.jar

Please note that RhodiumToad in #postgresql on irc.freenode.org actually
discovered this based on a conversation he, ojacobson, and I had, and I'm
simply reporting what he discovered.

Thanks,

Daniel

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] Error in 8.0 rc5 with repeat calls to array operator

[Daniel Ceregatti]

This doesn't happen on a fresh initdb. In fact, it doesn't happen even
directly after I load data. It might take a day or two, but eventually
the problem manifests itself. I can reproduce it 100% of the time now.
I've noticed this on 8rc1-5. Josh and I will get you a gdb trace ASAP.

Daniel

Tom Lane wrote:

  Josh Berkus  writes:
  
  
However, we're found that if you run thousands of empty array comparisons in a 
few seconds/minutes, eventually the empty array comparison breaks, and you 
get:
ERROR:  cache lookup failed for function 0

  
  
I tried

while true; do echo "select '{}'::INT[] = '{}'::INT[];" ; done | psql regression >/dev/null

on a couple different platforms, with and without INTARRAY (which
isn't invoked by this query anyway, so I doubt it matters).  I haven't
seen any misbehavior yet.

If you can reproduce this, please attach to the backend with gdb, set a
breakpoint at errfinish(), and get a stack traceback from the point of
the error.

			regards, tom lane