Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbJzk-00027a-KT for pgsql-performance@arkaria.postgresql.org; Wed, 20 May 2020 08:22:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jbJzj-0006Hx-GI for pgsql-performance@arkaria.postgresql.org; Wed, 20 May 2020 08:22:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbJzj-0006Hq-53 for pgsql-performance@lists.postgresql.org; Wed, 20 May 2020 08:22:31 +0000 Received: from mail-ed1-x541.google.com ([2a00:1450:4864:20::541]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jbJzg-0000nX-4O for pgsql-performance@lists.postgresql.org; Wed, 20 May 2020 08:22:30 +0000 Received: by mail-ed1-x541.google.com with SMTP id d24so2023270eds.11 for ; Wed, 20 May 2020 01:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=loC0XUQ/0r2zN1rHMT37sOOpn++xz5R53aiQ3X37C0w=; b=F/RV+Xo4mV1wXuYg/Ut6dSYYVwZmEClBLzEqufFNEJyTaHjaN8YSl0bQzq42O9TJan r1LP+bW26/uKOQUbEaLpSWgHDHDII0b5+xCz0LsGKuyrSm7bqO6pcQlhvPHJLd553lMO hFMtPGeje5jnKdibaYX6XpUIy2Vj9jwIqK/ouA5qRolsD+v93ZqykzQxsHDYuG2usb3L +xlLzDNVZskW0LonwXw7LfbG5ciG20vvJ2R3AmibuuKLxnIXLe7AbrnHD27hQjMTPzW1 yMfl6ELe+K/rmwVzqkXnb7R2AMhoPmjLFOJhyAxaw7ieLsKijATS68dPCyDSa4Dl6qDI 2mhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=loC0XUQ/0r2zN1rHMT37sOOpn++xz5R53aiQ3X37C0w=; b=ulKtgIB8DZGkGT/N6hsnMAZpwyeBV/QWu/XUQ4ZhEplZ8tngY7c1yMtUik32sQrs68 biuXq3lP5Q56wzgm2FdIPsGGWg6uz4RifO390t98QCJC3VDq4ze3IpARa2JD4+wEd2fe edHkzwnQY0KxOeEUZdUJ4gGciKnbFQGuXBw2hw1PR09CMtJU7/PzEb7YE4ScOYjnbYtR lXRx+h5NMuQLzzBLJ4XFoEb41NCUK5lQ56TmIBs8dnBtucbaONYzDkegFWT4ydnv4aup sUpS16KgHwwDQkPlKiMUqWL0/4kO2XxRcpb3WDMWBzeG2FnYWMXHmZri6bb6CkV0MaRl L5MQ== X-Gm-Message-State: AOAM533/x74JzoeE3fa42twrWpNSTUYHQOCY8VSdZkfVLR0Tv4+Q98Sv 8tORW4+sVgL1A/RqTnPvd3RSbw== X-Google-Smtp-Source: ABdhPJyRFdupkEz9SSmHBKg4nHLD7llAnD09TBNsfJ7NuVZYtqLAvixVHZm0r+ebewncD5MixuI2Ng== X-Received: by 2002:a50:f111:: with SMTP id w17mr2438582edl.41.1589962946485; Wed, 20 May 2020 01:22:26 -0700 (PDT) Received: from dynamic-eotlmt57cxwt1wzm9-pd01.res.v6.highway.a1.net (dynamic-eotlmt57cxwt1wzm9-pd01.res.v6.highway.a1.net. [2001:871:60:b467:23a6:b9e0:a2d5:f151]) by smtp.gmail.com with ESMTPSA id b15sm1176143edj.37.2020.05.20.01.22.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 May 2020 01:22:25 -0700 (PDT) Message-ID: Subject: Re: OOM Killer kills PostgreSQL From: Laurenz Albe To: Piotr =?UTF-8?Q?W=C5=82odarczyk?= , pgsql-performance@lists.postgresql.org Date: Wed, 20 May 2020 10:22:24 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 2020-05-20 at 09:30 +0200, Piotr Włodarczyk wrote: > We met unexpected PostgreSQL shutdown. After a little investigation > we've discovered that problem is in OOM killer which kills our PostgreSQL. > Unfortunately we can't find query on DB causing this problem. Log is as below: Is there nothing in the PostgreSQL log? Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com