Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 90D421FA2A4B for ; Thu, 26 Jul 2012 05:40:20 -0300 (ADT) Received: from intern.proventis.net ([85.182.161.50]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SuJc9-0004HW-Ct for pgsql-admin@postgresql.org; Thu, 26 Jul 2012 08:40:19 +0000 Received: from mail.proventis.net (unknown [192.168.22.239]) by intern.proventis.net (Postfix) with ESMTP id 3CB652B5D0 for ; Thu, 26 Jul 2012 10:39:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.proventis.net (Postfix) with ESMTP id 228441D8B3D for ; Thu, 26 Jul 2012 10:39:56 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.proventis.net Received: from mail.proventis.net ([127.0.0.1]) by localhost (mail.proventis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxWkiNkwewdb for ; Thu, 26 Jul 2012 10:39:55 +0200 (CEST) Received: from [192.168.22.130] (tmarkus.proventis.net [192.168.22.130]) by mail.proventis.net (Postfix) with ESMTP id 9F60C1D7282 for ; Thu, 26 Jul 2012 10:39:55 +0200 (CEST) Message-ID: <5011025B.7050003@proventis.net> Date: Thu, 26 Jul 2012 10:39:55 +0200 From: Thomas Markus Organization: proventis GmbH User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: problems with access into system catalogs References: <5010F555.9020209@proventis.net> <5010FEF2.3050901@ringerc.id.au> In-Reply-To: <5010FEF2.3050901@ringerc.id.au> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/83 X-Sequence-Number: 39800 Hi, see below Am 26.07.2012 10:25, schrieb Craig Ringer: > First, thank-you for an excellent complete question with versions, > EXPLAIN ANALYZE, and exact messages. ;) > > - Do you have any uncommitted two phase transactions? Run: > SELECT * from pg_prepared_xacts ; hm yes, i stopped all applications this morning but this query shows: transaction | gid | prepared | owner | database -------------+----------------------------------------------------------------------------------------------+-------------------------------+--------+----------- 49737548 | 131075_MS03ZjAwMDAwMTpjZmVlOjRlZDg3MTk2OjY4NGJlN2I=_N2YwMDAwMDE6Y2ZlZTo0ZWQ4NzE5Njo2ODRiZTdm | 2012-01-05 07:49:30.78583+01 | xxx | db1 49737549 | 131075_MS03ZjAwMDAwMTpjZmVlOjRlZDg3MTk2OjY4NGJlN2I=_N2YwMDAwMDE6Y2ZlZTo0ZWQ4NzE5Njo2ODRiZTg0 | 2012-01-05 07:49:30.789382+01 | xxx | db2 system time is valid (Thu Jul 26 10:38:12 CEST 2012). so may 1st is really old Should I restart the instance? > > - Do you have any long-lived 'IDLE IN TRANSACTION' connections ? Try: > SELECT * FROM pg_stat_activity WHERE current_query = ' in > transaction' AND xact_start > current_timestamp - '1 minute'::interval; none, and there was a disconnect from all clients this morning > > Either of those can prevent vacuum from cleaning things up. > > Do you very frequently create and drop tables, indexes, etc? Say, > using a database unit testing framework? no, its a live system with normal olap access Thomas