Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaUE7-0003kL-9C for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2014 18:06:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WaUE6-0007AH-Ir for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2014 18:06:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaUE5-0007A8-HD for pgsql-hackers@postgresql.org; Wed, 16 Apr 2014 18:06:25 +0000 Received: from smtp.01.com ([199.36.142.181]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaUE2-0000sE-Aq for pgsql-hackers@postgresql.org; Wed, 16 Apr 2014 18:06:25 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 3C966296A1E; Wed, 16 Apr 2014 13:06:21 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8lfKerhfVPo; Wed, 16 Apr 2014 13:06:21 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 17888296A59; Wed, 16 Apr 2014 13:06:21 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id F39B9296A50; Wed, 16 Apr 2014 13:06:20 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DokBH2w_DuKT; Wed, 16 Apr 2014 13:06:20 -0500 (CDT) Received: from [192.168.47.107] (50-1-62-16.dsl.dynamic.sonic.net [50.1.62.16]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 7103E296A1E; Wed, 16 Apr 2014 13:06:20 -0500 (CDT) Message-ID: <534EC69B.9010107@agliodbs.com> Date: Wed, 16 Apr 2014 11:06:19 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Alvaro Herrera CC: pgsql-hackers@postgresql.org Subject: Re: Need Multixact Freezing Docs References: <534DA3D1.2010000@agliodbs.com> <534DB22A.2040909@agliodbs.com> <20140416133233.GL5822@eldon.alvh.no-ip.org> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org > You can see the current multixact value in pg_controldata output. Keep > timestamped values of that somewhere (a table?) so that you can measure > consumption rate. I don't think we provide SQL-level access to those > values. Bleh. Do we provide SQL-level access in 9.4? If not, I think that's a requirement before release. Telling users to monitor a setting using a restricted-permission command-line utility which produces a version-specific text file they have to parse is not going to win us a lot of fans. > >> Also: how do I check the multixact age of a table? There doesn't seem >> to be any data for this ... > > pg_class.relminmxid is the oldest multixact value that might be present > in a table. On every database I've tested, age(relminmxid) returns int_max. So this is apparently broken. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers