Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bhOuf-0006Vh-TJ for pgsql-docs@arkaria.postgresql.org; Tue, 06 Sep 2016 22:32:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bhOuf-0002lP-Al for pgsql-docs@arkaria.postgresql.org; Tue, 06 Sep 2016 22:32:17 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bhOuI-0002N0-Vn for pgsql-docs@postgresql.org; Tue, 06 Sep 2016 22:31:55 +0000 Received: from newmail.postgrespro.ru ([93.174.131.138] helo=mail.postgrespro.ru) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bhOuF-00059V-Ry for pgsql-docs@postgresql.org; Tue, 06 Sep 2016 22:31:53 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 76EE021C2811 for ; Wed, 7 Sep 2016 01:31:49 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru Received: from mail.postgrespro.ru ([127.0.0.1]) by localhost (mail.postgrespro.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zk9uIfLELF11 for ; Wed, 7 Sep 2016 01:31:49 +0300 (MSK) Received: from [192.168.1.38] (broadband-46-188-127-44.2com.net [46.188.127.44]) by mail.postgrespro.ru (Postfix) with ESMTPSA id 443B821C2785 for ; Wed, 7 Sep 2016 01:31:49 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1473201109; bh=xSDKxQ+gXwk8z73L8Zoy3cWjNGn0jjBU3JVgU5KMldM=; h=Subject:To:References:From:Date:In-Reply-To; b=aUpNDjLWjNw3fbWVl882iXTkucamE5iqFJm3fn65nvNuR4zMt3YirqZdyLv3gx6V4 D6GRKNo1JcmK95TOdRej+gVY0H7eEHbvOQtXYr6An4+1MCHkJqrJqkIQdT9p25WQmW n85r023FGrT9mMCTr+qbXAdUkU2XvetClS9TBuyY= Subject: Re: FrozenTransactionId To: pgsql-docs@postgresql.org References: <575D7955.6060209@postgrespro.ru> <1473096445753-5919545.post@n3.nabble.com> <31833.1473097584@sss.pgh.pa.us> <57CDED18.8060005@postgrespro.ru> <57CE6F15.4060101@postgrespro.ru> <16060.1473165694@sss.pgh.pa.us> <57CF23F9.10304@postgrespro.ru> <18782.1473194499@sss.pgh.pa.us> From: Egor Rogov Message-ID: <57CF43D5.7080306@postgrespro.ru> Date: Wed, 7 Sep 2016 01:31:49 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <18782.1473194499@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -3.1 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 06.09.2016 23:41, Tom Lane wrote: > Egor Rogov writes: >> Right, it does not say that FrozenTransactionId is what appears on disk, >> but what is? There is no such information anywhere in the doc. Since 9.4 >> frozen transactions have their normal XIDs preserved, so how a user can >> tell normal transaction from frozen one? This is what needs to be >> explained, I believe. > I'm afraid the answer is "you can't tell". The infomask bits in tuple > headers aren't exposed via SQL. If you're really desperate, > contrib/pageinspect would help, but I don't propose mentioning that here. > > In general, I'm not really sure why users would care very much at > a tuple-by-tuple level. "Normal" users shouldn't care of course, but DBAs sometimes have to. The old description could be easily misunderstood and one might expect to see FrozenTransactionId in xmin field (I know several people who wasted hours trying to figure out what's wrong with vacuum freeze). Now the description is much cleaner, thanks! > Aggregate statistics would be interesting, > which raises the question why contrib/pgstattuple doesn't provide > frozen-tuples counts. > > regards, tom lane > > Regards, Egor Rogov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs