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 1lp6UF-0007Xk-0T for pgsql-admin@arkaria.postgresql.org; Fri, 04 Jun 2021 09:51:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lp6UD-0004DN-W9 for pgsql-admin@arkaria.postgresql.org; Fri, 04 Jun 2021 09:51:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lp6UD-0004DF-In for pgsql-admin@lists.postgresql.org; Fri, 04 Jun 2021 09:51:29 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lp6U7-0005gf-1K for pgsql-admin@lists.postgresql.org; Fri, 04 Jun 2021 09:51:29 +0000 Received: by mail-ej1-x634.google.com with SMTP id ho18so2599026ejc.8 for ; Fri, 04 Jun 2021 02:51:22 -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=zTT6hTwNE9rj5w+vAcXt4z5VlkdYCLsq3q+fZpyxjFA=; b=CdN1XWsnmUo9j3Z3QBlDZGr/sv22LRM8fPu60n8yY2kHBPRyblOqeRdwisG6um/y/4 UM98iLmzTurk74ESStcwMe9TWYOOzbrL5SzAY5pkRT2HF3uZtGEeVLTX7hc5WaVvLNut nA69U4VJTPMy0xRxroZdxmPs75TjfCpDIPki+eb+ma752Yh8Dww5YQFFu2tegDIJL2WK K6Ib4TuIf/kj9zyWAB429KTtkRoD5NQQsNNzzXMmZQlgUkk9bh1UZYBBtP0i1LOF59kP +Le5YC0rgBLFUW52otAKMWawgavSm3PAACf3LCmf47GD0NHV83x2anaXHIJ89tTiMENV P24w== 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=zTT6hTwNE9rj5w+vAcXt4z5VlkdYCLsq3q+fZpyxjFA=; b=CubAogttfvrc1pxXjHhp8TxJcz1BKKIvBY4sv36s8q2HhuT3KS+uy0PHmsNFtvqHOE rkGzuYvVoRHG/3Fik83TOgn1yOdi/42oS4iVKEX2T631DfwKl6poeHmOH9b3jewBDuZT Oiqp7l1o0/8UA8Oi7f1IeiMGYH5pflavy5cvl3m04/6ckffHsBJEEhxyBM0q3rvuBArX r85x8x0hcnuUMXZyXS4wtvoppTk9bzRIKk3QgZam7NTYLCSEO4UbpR/MwH2Qi/ldAeGr sIApNO3cDRkKYbksP0/2sBsEWCUw1JjyY3YWoOA5UU/gRQVJb1fJYXdn3Cfb8vI03Rcw MRkA== X-Gm-Message-State: AOAM5317beUHa6dJomjRNVa+tx9CZ5t2zvTpdYEIeyJebmsqM+mQTy2S dxDf4JWLMtFVLOa+2+NmK0gkYoIrzbk40A== X-Google-Smtp-Source: ABdhPJxHByVkPr2IBcMiNhi0n0O4XHOT2HkZUU+EdLJECxF4MAHQiz4iY1sVQe5SYX6pn4mu5OMCjw== X-Received: by 2002:a17:906:9bce:: with SMTP id de14mr3436872ejc.353.1622800281792; Fri, 04 Jun 2021 02:51:21 -0700 (PDT) Received: from localhost.localdomain (217-149-174-252.nat.highway.telekom.at. [217.149.174.252]) by smtp.gmail.com with ESMTPSA id dy19sm2964676edb.68.2021.06.04.02.51.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Jun 2021 02:51:21 -0700 (PDT) Message-ID: <3796904db4aa6f124918c9bb66288d2bc3185a7f.camel@cybertec.at> Subject: Re: Killed background writer process From: Laurenz Albe To: Raj kumar , Pgsql-admin Date: Fri, 04 Jun 2021 11:51:20 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2021-06-04 at 14:54 +0530, Raj kumar wrote: > I've killed background writer process for a testing purpose. I found that after sometime > it automatically came up with a new PID without me doing anything from my end. > > How postgres automatically brings it up? Is there any impact on the Database and connections? The postmaster process keeps track of its children and restarts any background process that died. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com