Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaXRy-0004Uz-Jn for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2014 21:32:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WaXRx-0002YL-Ip for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2014 21:32:57 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaXRw-0002YC-1j for pgsql-hackers@postgresql.org; Wed, 16 Apr 2014 21:32:56 +0000 Received: from smtp.01.com ([199.36.142.181]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaXRp-0004vz-3V for pgsql-hackers@postgresql.org; Wed, 16 Apr 2014 21:32:55 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 9BB893983A6; Wed, 16 Apr 2014 16:32:48 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQGeMhF_87_J; Wed, 16 Apr 2014 16:32:48 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 7FE323995E3; Wed, 16 Apr 2014 16:32:48 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 6A02039959C; Wed, 16 Apr 2014 16:32:48 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6qYdk7mSCofB; Wed, 16 Apr 2014 16:32:48 -0500 (CDT) Received: from [10.100.2.8] (199-116-73-3.sfo1.office.zencoderdns.net [199.116.73.3]) by smtp-out-2.01.com (Postfix) with ESMTPSA id EF7B03983A6; Wed, 16 Apr 2014 16:32:47 -0500 (CDT) Message-ID: <534EF6FC.80804@agliodbs.com> Date: Wed, 16 Apr 2014 14:32:44 -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> <534EC69B.9010107@agliodbs.com> <20140416203057.GQ5822@eldon.alvh.no-ip.org> <534EEA8E.5070407@agliodbs.com> <20140416204538.GR5822@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 >> So if age() doesn't mean anything, then how are users to know when the >> need to freeze? > > I don't understand. Autovacuum will freeze this automatically when the > threshold is reached. Users don't need to do anything. What I'm asking is: - how do users know if Autovacuum is keeping up with multixact feezing? - how do users get data on multixact usage so that they can tune the parameters? -- 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