From: Gnanakumar <gnanam@zoniac.com>
To: pgsql-admin@postgresql.org
Subject: Re: Temporary table failed to drop after power failure
Date: Wed, 16 Mar 2011 15:01:37 +0530
Message-ID: <002f01cbe3bc$f4af5840$de0e08c0$@com> (raw)
In-Reply-To: <006f01cbe21f$35a217b0$a0e64710$@com>
References: <006f01cbe21f$35a217b0$a0e64710$@com>
Any ideas/recommendation?
-----Original Message-----
From: Gnanakumar [mailto:gnanam@zoniac.com]
Sent: Monday, March 14, 2011 1:40 PM
To: pgsql-admin@postgresql.org
Subject: Temporary table failed to drop after power failure
Hi,
We're using PostgreSQL v8.2.3. Ours is a web-based application, language is
Java and we're using pgpool-II v 2.0.1 purely for connection pooling (we
don't use other features of pgpool like Replication, Load Balancing, etc.).
We're creating temporary table using "CREATE TEMP TABLE FOO(col1, col2,
...)" and it's being heavily used in one of our application report. When
the report was still running, suddenly there was a power failure and
PostgreSQL was stopped abruptly without proper shutdown. Now, if run the
following system catalog queries, I can see that those temporary tables were
not dropped really:
1) SELECT schemaname, tablename, pg_size_pretty(size) AS size_pretty,
pg_size_pretty(total_size) AS total_size_pretty FROM (SELECT *,
pg_relation_size(schemaname||'.'||tablename) AS size,
pg_total_relation_size(schemaname||'.'||tablename) AS total_size FROM
pg_tables where tablename = 'foo') AS TABLES ORDER BY total_size DESC;
2) select * from pg_stat_user_tables where relname = 'foo';
Now, how do I fix/handle in this situation?
Although this happened within our staging environment, I look forward to
experts advice/recommendation before I conclude anything.
Regards,
Gnanam
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-admin@postgresql.org
Cc: gnanam@zoniac.com
Subject: Re: Temporary table failed to drop after power failure
In-Reply-To: <002f01cbe3bc$f4af5840$de0e08c0$@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