Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNe31-0004oI-PZ for pgsql-admin@arkaria.postgresql.org; Mon, 06 May 2019 13:52:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hNe30-0003gw-8G for pgsql-admin@arkaria.postgresql.org; Mon, 06 May 2019 13:52:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNe2z-0003dH-Ob for pgsql-admin@lists.postgresql.org; Mon, 06 May 2019 13:52:49 +0000 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNe2x-0005SA-BI for pgsql-admin@postgresql.org; Mon, 06 May 2019 13:52:48 +0000 Received: by mail-lf1-x130.google.com with SMTP id j20so9229337lfh.2 for ; Mon, 06 May 2019 06:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=mRaSVC2fPK3qwhNiDB30jfjpTYlEep8Q75k5bDa+apI=; b=HGHiBvZNtcAVV9xfl3TL0NO8wSuoYJOBV1HLvWlZaskvDWw0Pq5pMgLFJJq90CzoyH 3/e0djizuFqmuoiDVV6UqLfoH6P6T9+eit+3yodMU4mMFjxSEKdb0NvSIUd/b2ZmhGel 4dN+kQaI7f3rAcxJfRpd6fM0odJz8798SRQscEv64HeyyPo380BO/WgA43ZaHJ/A5OVI A2nm2EtAaOjt799sAYvvuVGrx1pB5ufZkoXiDf7NO7vyDRlzSqNAYtkp0s7Odw6L8fSt bczjOfgNWMfRKR3b/G1S5JwPNWSj7RzI+GbMLu5GAihTiI/EzG5wgoddwvZKek+FcbLt Se6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=mRaSVC2fPK3qwhNiDB30jfjpTYlEep8Q75k5bDa+apI=; b=ZnSZJ52zUjZj0yE0fygtj9e1h8QZ6ZIHnANjOfRk15WD1K+NzmTtJBKDz9ekGmzNEv ppdAgmfK2kKG+EQIm/a9o7rAssZs1aj3mXdIXZHePw8NhxipLJ0mBxjwLwP/P7XmgJQX QMrCH3YDy8ZGm54SCn2bnfb4BjxcAY2LhTkTaS7Tr6kQGaUFKW5/GfHao8kH2wmcI9Ul xgDCT6NKwE7a+gzKvCqwyTk1xf6j73+1+ELiQtbYpLRRejQx5vWdb0UF7aZSKxcL3DD7 QQRXc9KXduv6BAMt/RoaQBzThlHkFUJ6Ib+p0KxkLlDOsz4PeAP8c5c5Z054nkZeQ7QM R+6w== X-Gm-Message-State: APjAAAUMXOuOsU8GFSplDa83KEnopvMOrleFWViWJSrko4xGUxPFE9Rh sn4xquMivQsHKls2m4TIRCJSzn4LLg== X-Google-Smtp-Source: APXvYqy6v61/gBKo8VgsFs+Ndf4nX8sd9CxPeKYc75QwRL6nFSFLenFXRvt9efndoQL1ReU5AjQgXQ== X-Received: by 2002:ac2:550f:: with SMTP id j15mr6093800lfk.73.1557150764006; Mon, 06 May 2019 06:52:44 -0700 (PDT) Received: from [10.101.35.126] (fg.grupainteger.pl. [91.216.25.78]) by smtp.gmail.com with ESMTPSA id s6sm2373746ljh.65.2019.05.06.06.52.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 May 2019 06:52:43 -0700 (PDT) To: pgsql-admin@postgresql.org From: Aleksandra Angielska Subject: problems after vacuum full Message-ID: <168917fb-b9bb-231a-e243-9b959423994f@gmail.com> Date: Mon, 6 May 2019 15:52:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, We have a virtual machine (VMware ESXi 6.5 U2): OS: 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux PG: PostgreSQL 9.6.5 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit A database was working for a few months and I did a vacuum full on one table. A table had about ~160 GB of data and the same amount of indexes. After vacuum full was successful a table was emptied - SELECT on it returned 0 rows, but not an error. During the OS analysis, we discovered differences between du and df commands that indicated there were deleted files with open handlers. Command 'lsof' displayed postmaster as PID holding the handlers. We would like to know if somebody had similar issues? We are afraid that it would happen to us again. We are aware of the fact that we should make an upgrade, but we are currently unable to do so. We would appreciate if you could give us any suggestions. Best regards Aleksandra Angielska