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 1gO6GX-0001ew-Dx for pgsql-admin@arkaria.postgresql.org; Sat, 17 Nov 2018 19:28:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gO6GV-0007Fl-Lb for pgsql-admin@arkaria.postgresql.org; Sat, 17 Nov 2018 19:28:23 +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 1gO6GV-0007Fd-AN for pgsql-admin@lists.postgresql.org; Sat, 17 Nov 2018 19:28:23 +0000 Received: from mx1.mailbox.org ([2001:67c:2050:104:0:1:25:1]) by makus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gO6GR-00079O-Bf for pgsql-admin@lists.postgresql.org; Sat, 17 Nov 2018 19:28:21 +0000 Received: from smtp2.mailbox.org (unknown [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id B0BEB4370F; Sat, 17 Nov 2018 20:28:12 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter06.heinlein-hosting.de (spamfilter06.heinlein-hosting.de [80.241.56.125]) (amavisd-new, port 10030) with ESMTP id RI2l0aCDi3Lx; Sat, 17 Nov 2018 20:28:11 +0100 (CET) Message-ID: <69cd4eb6a9686eab9319f864db15942ec06fe86c.camel@cybertec.at> Subject: Re: checkpoint occurs very often when vacuum full running From: Laurenz Albe To: Mariel Cherkassky Cc: Sergei Kornilov , pgsql-admin@lists.postgresql.org Date: Sat, 17 Nov 2018 20:28:10 +0100 In-Reply-To: References: <6028761542309042@myt3-c573aa6fc782.qloud-c.yandex.net> <77addc59000b6e152c44aad3b1b9f739e025973b.camel@cybertec.at> Organization: Cybertec Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Mariel Cherkassky wrote: > thank you for the explanation but I still got a few questions about this subject : > 1.By physical location of the data do you mean the location on disk of the objects? > I mean i thought that the wal files containing the logical changes , for example > If I run an update then the wal file will contain the update in some format. > Can you explain then what exactly it contains and what you meant by physical ? It does *not* contain the SQL executed - how'd that work with functions like "random"? Rather, the information is like "replace the 42 bytes from offset 99 of block 12 in file xy with these bytes: ...". > 2.So If the vacuum full stopped in some brutal way (kill -9 or the disk run of space) > does all the new data files that are created deleted or left on the storage as orphan files ? In an out of space scenario, the files would get removed. If you kill -9 the backend they will be left behind. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com