Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1behsV-0005Gt-2u for pgsql-admin@arkaria.postgresql.org; Tue, 30 Aug 2016 12:10:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1behsU-000589-BY for pgsql-admin@arkaria.postgresql.org; Tue, 30 Aug 2016 12:10:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1behrN-00053Q-8x for pgsql-admin@postgresql.org; Tue, 30 Aug 2016 12:09:45 +0000 Received: from nm39.bullet.mail.ir2.yahoo.com ([212.82.96.64]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1behrJ-00013g-M8 for pgsql-admin@postgresql.org; Tue, 30 Aug 2016 12:09:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1472558979; bh=cNM9gzFzPExdxhZn/2UKbfdLOGT5jUMKYYvAZ3P9RtM=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=MG9sUxlK9GnB+/y3zvmxPeyLPidT3R9BkQeOs7vrTn4rR9c+Ur+ltmhc2zWlcb4mImxj4OJhgq8xq03IXH7bdnP/nKslvyGUfsoKXB50EWoRq+OEuU4ufGRj4cnb9EKiBIyChDgM3nKwGSr0fpijHNFPQD9b53xc5HAHNObWmD/928CA/hmXZz246psfYFqXkbrDaeIicEFz/VqGoyMGd3WPeb69G3LQ8/CukJi5stX7UBuGHwUCR7W4JG/9J5w1pr0LxjQlrOUKJRF1nJZ75EF97gWdaU454K7uegOvcc37FLawnJICyuQjhauiF/WPYnTkf6WpldqdejT1nCmXEg== Received: from [212.82.98.57] by nm39.bullet.mail.ir2.yahoo.com with NNFMP; 30 Aug 2016 12:09:39 -0000 Received: from [212.82.98.90] by tm10.bullet.mail.ir2.yahoo.com with NNFMP; 30 Aug 2016 12:09:39 -0000 Received: from [127.0.0.1] by omp1027.mail.ir2.yahoo.com with NNFMP; 30 Aug 2016 12:09:39 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 741644.2206.bm@omp1027.mail.ir2.yahoo.com X-YMail-OSG: M_VtFe4VM1lTisC.MvGTr9rp6jDKiwWAseA.xuh8LMJsg6rT3GQtFM7YuMogjFJ TmJos0QZZcFJ.9bVdZaNonDUKTHhcy6uk2FU7mewA6Qo5yIsVHUQ_zfP3TDL2yXCxwlw.1b.8niY YbnhFTDJEItr5ZNPYsDCZeeOE.pDGhJHecxPUo93ACN2dVTX7F2f.e0FNMACWz5PHKeJRH3f1hn9 sqxNbx_2rT90I3m1q12tmZ.i5zxWqCf3GA0R3ld5_WXbmz8QFaVsbBdOM8Wc8yq5KbA5C7Ym5FZq 5P3bIff.iSiugWHPp9Q.GlTh8BDwagWWg2yrQeFZeF78FILYaOudSI3Klwhm9AUDd_.K_gQZpqht pkPU7dSIStd65N33ShdaIHdWt38uMlKD1ZL2i6Za9u47eFVEcaLgZ1NzYEywfXemG2V9Xq0hrEKV KosFJrecnRv7eSz1aRyR0h1vzinQHCjh8eURRJ2L1jLtpKcvKf.8acT60EDcZd9SR2vpBK5vrILU Fhecc2HU0HJhckUzInxK60GMx Received: from jws11128.mail.ir2.yahoo.com by sendmailws167.mail.ir2.yahoo.com; Tue, 30 Aug 2016 12:09:39 +0000; 1472558979.211 Date: Tue, 30 Aug 2016 12:09:37 +0000 (UTC) From: Ben Kammer Reply-To: Ben Kammer To: "pgsql-admin@postgresql.org" Message-ID: <1940442054.3299228.1472558977138@mail.yahoo.com> Subject: Vacuum freeze help MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3299227_794798860.1472558977133" References: <1940442054.3299228.1472558977138.ref@mail.yahoo.com> Content-Length: 6228 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ------=_Part_3299227_794798860.1472558977133 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, I have a postgresql 9.5.4 cluster and was testing with vacuum freeze. I exp= ected the value of xmin to be set to '2' when I vacuum a particular table w= ith the VACUUM FREEZE command. But for some reason this doesn't happen. Her= e is my small test: test=3D# create table t1 (col1 int, col2 int);CREATE TABLEtest=3D# insert i= nto t1 values (1,2), (3,4);INSERT 0 2test=3D# select xmin, xmax, * from t1;= =C2=A0xmin | xmax | col1 | col2=C2=A0------+------+------+------=C2=A01845 = |=C2=A0 =C2=A0 0 |=C2=A0 =C2=A0 1 |=C2=A0 =C2=A0 2=C2=A01845 |=C2=A0 =C2=A0= 0 |=C2=A0 =C2=A0 3 |=C2=A0 =C2=A0 4(2 rows) test=3D# vacuum freeze t1;VACUUMtest=3D# select xmin, xmax, * from t1;=C2= =A0xmin | xmax | col1 | col2=C2=A0------+------+------+------=C2=A01845 |= =C2=A0 =C2=A0 0 |=C2=A0 =C2=A0 1 |=C2=A0 =C2=A0 2=C2=A01845 |=C2=A0 =C2=A0 = 0 |=C2=A0 =C2=A0 3 |=C2=A0 =C2=A0 4(2 rows)=C2=A0As you can see from the re= sults of the last select statement the value of xmin is 1845 instead of 2 w= hich I expected it to be. On my 9.0 cluster this works fine. Has this behav= ior of postgresql been changed since 9.0? Can anyone explain this? Ben. ------=_Part_3299227_794798860.1472558977133 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I have a postgresql 9.5.4 clust= er and was testing with vacuum freeze. I expected the value of xmin to be s= et to '2' when I vacuum a particular table with the VACUUM FREEZE command. = But for some reason this doesn't happen. Here is my small test:

test=3D# c= reate table t1 (col1 int, col2 int);
CR= EATE TABLE
test=3D# insert into t1 valu= es (1,2), (3,4);
INSERT 0 2
test=3D# select xmin, xmax, * from t1;
 xmin | xmax | col1 | col2 
=
------+------+------+------
 1845 |    0 |    1 |    2<= /span>
 1845 |    0 |  &nb= sp; 3 |    4
(2 rows)<= /div>

test=3D# vacuum freeze t1;
VACUUM
test= =3D# select xmin, xmax, * from t1;
&nbs= p;xmin | xmax | col1 | col2 
-----= -+------+------+------
 1845 |&nbs= p;   0 |    1 |    2
 1845 |    0 |    3 |    4=
(2 rows)
 
As yo= u can see from the results of the last select statement the value of xmin i= s 1845 instead of 2 which I expected it to be. On my 9.0 cluster this works= fine. Has this behavior of postgresql been changed since 9.0? Can anyone e= xplain this?


Ben.



------=_Part_3299227_794798860.1472558977133--