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 1igvtq-0000Uk-8l for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Dec 2019 19:19:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1igvtn-0005pE-I4 for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Dec 2019 19:19:19 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1igvtn-0005p7-6N for pgsql-bugs@lists.postgresql.org; Mon, 16 Dec 2019 19:19:19 +0000 Received: from mail-pg1-x543.google.com ([2607:f8b0:4864:20::543]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1igvtk-0001Io-D5 for pgsql-bugs@lists.postgresql.org; Mon, 16 Dec 2019 19:19:18 +0000 Received: by mail-pg1-x543.google.com with SMTP id k25so4253296pgt.7 for ; Mon, 16 Dec 2019 11:19:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=BzdaGouoONhmrP/pYqa+pS+Dp9nZXW1QQr9XGfoety0=; b=Vd4gnbsMlfpyJ0WeLBSgQSpBI2fQ3kBXTQdGiPoibHxu5T922rD9bc/GqwhwHklJxa r8NRnfIeIycLMy4UtUqbpepxAtLsjYUCcuOWYFbFm2k/s7iVqcJrzShCB/I9bxaBB4E/ qak/+0mrKLcUN4DBQm6/u39H0iLeLQYO78I0kqdLkRN9Jkt5XNBXem7zTJF9GQtG7Uhz ySqObeQ3EaDK1ytyzDfhwhY52RghyLBpifLhnNT71eDqcR6GSuly7n5anbumbCyq3+6T FRYQp27dDV0FsQt3M1X7mgaaBAN0g9ueYmxeJc+UTPSfeebzehgunR8NzcjA81ita8HK WnrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=BzdaGouoONhmrP/pYqa+pS+Dp9nZXW1QQr9XGfoety0=; b=LDRJ4LEPTbocjDIam2pFB9JAj/ahfP4NmTn0ocP1wozrXfN4UaviiYFxMLy50tHH5H unq8+0zYuCUelwAdQ1lYzB3uQijhNhrrrf65Bi31c1ocGX/NdN30ys5SmJ+VD2jYszNB KLvKUj7iX6zf25LSfLgd8PueuVhsF+GQLWaYSsTjfaBYS+lhZWnIJYG1GAbCB76p5AcQ BRcci0C3muxut3cvWopqwliDqzTL1qSCNvkA8ZG8vPSximrKaSEne/uevT1FTT/6BROa 7Bg67K+HO7XvnEmfJsaNv/3vJtuHi7UR8NHzR/qwc1d25XG49quEaX36W+WlBFHPcG8r yKOw== X-Gm-Message-State: APjAAAWS05t+36KMYm2SYoBVPwrWiKcACNi8X7Vy7CdgXaOWHc6aM53s 2bocdxPkecQ2RyAtMd6MJBrH4bCrsJDERR4YH6hGvr5yJVH8b8otz/l4LUxnlDe6izVdj7EIvX6 D1POcZ0kjD5XybrG6eHGPbKvlMAawRGPm5a49gAoNpQTCJ4HJSquA+T7celP0U2qfdBt82NqPTo PLNNa7xFD6SXA2 X-Google-Smtp-Source: APXvYqyUz+SonDsCocUnrwX6GHhWGZ36WsI+k58IWjPtSpBfogatT/p7jazY6aPxC/w+lGtnNcC79Q== X-Received: by 2002:a62:e40e:: with SMTP id r14mr17602032pfh.115.1576523954055; Mon, 16 Dec 2019 11:19:14 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([179.56.30.174]) by smtp.gmail.com with ESMTPSA id e10sm24003940pfm.3.2019.12.16.11.19.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Dec 2019 11:19:13 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 33E6D3006A1; Mon, 16 Dec 2019 16:19:11 -0300 (-03) Date: Mon, 16 Dec 2019 16:19:11 -0300 From: Alvaro Herrera To: Jens.Wilke@parcIT.de Cc: pgsql-bugs@lists.postgresql.org Subject: Re: Missing locales prevent autovacuum Message-ID: <20191216191911.GA8643@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201912161800.xBGI0R8U027003@mail-srz-p-02.noc.fiducia.de> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Dec-16, Jens.Wilke@parcIT.de wrote: > is it intended, that missing locales of single databases prevent autovacuum > in the entire cluster? > FATAL: database locale is incompatible with operating system > If so, shouldn't there be an ERROR instead or additionally? Probably that database is in danger of XID wraparound, so autovacuum is selecting it without regard for any other databases. Keeping broken databases in your cluster is definitely not a good idea. I suggest you DROP it to allow other things to work normally. Yes, I think we should somehow fix this problem. But nobody has attacked it seriously enough yet. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services