Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaWiP-0002C3-9M for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2014 20:45:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WaWiO-0008KR-J9 for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2014 20:45:52 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaWiN-0008KI-1C for pgsql-hackers@postgresql.org; Wed, 16 Apr 2014 20:45:51 +0000 Received: from smtprelay0236.b.hostedemail.com ([64.98.42.236] helo=smtprelay.b.hostedemail.com) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WaWiD-00045Y-Lr for pgsql-hackers@postgresql.org; Wed, 16 Apr 2014 20:45:50 +0000 Received: from filter.hostedemail.com (b-bigip1 [10.5.19.254]) by smtprelay06.b.hostedemail.com (Postfix) with ESMTP id C0DD58D29E; Wed, 16 Apr 2014 20:45:40 +0000 (UTC) X-Session-Marker: 616C76686572726540616C76682E6E6F2D69702E6F7267 X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, alvherre@alvh.no-ip.org, :::, RULES_HIT:41:69:355:379:599:965:966:967:973:988:989:1260:1277:1311:1312:1313:1314:1345:1359:1437:1515:1516:1518:1519:1534:1541:1593:1594:1595:1596:1711:1730:1747:1777:1792:1801:2196:2199:2393:2525:2560:2563:2682:2685:2692:2693:2828:2859:2901:2912:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3352:3865:3866:3867:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4321:4385:4390:4395:4605:4659:5007:6261:9025:9036:9121:10004:10400:10848:11026:11232:11256:11257:11658:11914:12043:12135:12296:12517:12519:12555:12683:13069:13311:13357:13894:13895, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:none, Custom_rules:0:0:0 X-HE-Tag: smell98_1452c231af55a X-Filterd-Recvd-Size: 2834 Received: from eldon.alvh.no-ip.org (pc-151-72-104-200.cm.vtr.net [200.104.72.151]) (Authenticated sender: alvherre@alvh.no-ip.org) by omf13.b.hostedemail.com (Postfix) with ESMTPA; Wed, 16 Apr 2014 20:45:39 +0000 (UTC) Received: by eldon.alvh.no-ip.org (Postfix, from userid 1000) id 441D41FC9; Wed, 16 Apr 2014 17:45:38 -0300 (CLST) Date: Wed, 16 Apr 2014 17:45:38 -0300 From: Alvaro Herrera To: Josh Berkus Cc: pgsql-hackers@postgresql.org Subject: Re: Need Multixact Freezing Docs Message-ID: <20140416204538.GR5822@eldon.alvh.no-ip.org> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <534EEA8E.5070407@agliodbs.com> User-Agent: Mutt/1.5.21 (2010-09-15) 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 Josh Berkus wrote: > > Josh Berkus wrote: > >> > >>> 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. > > > > Yeah, good idea. Want to propose a patch? > > Yeah, lemme dig into this. I really think we need it for 9.4, feature > frozen or not. Great, thanks. > josh=# select relname, age(relminmxid) from pg_class; > relname | age > -----------------------------------------+------------ > pg_statistic | 2147483647 > pg_type | 2147483647 > random | 2147483647 > dblink_pkey_results | 2147483647 > pg_toast_17395 | 2147483647 > > ... > > 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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers