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 1iQxEt-0004EY-Sr for pgsql-bugs@arkaria.postgresql.org; Sat, 02 Nov 2019 17:31:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iQxEq-0000XO-A4 for pgsql-bugs@arkaria.postgresql.org; Sat, 02 Nov 2019 17:31:00 +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 1iQxEp-0000VC-SD for pgsql-bugs@lists.postgresql.org; Sat, 02 Nov 2019 17:31:00 +0000 Received: from mail-pg1-x535.google.com ([2607:f8b0:4864:20::535]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iQxEm-0003LV-Tf for pgsql-bugs@lists.postgresql.org; Sat, 02 Nov 2019 17:30:58 +0000 Received: by mail-pg1-x535.google.com with SMTP id 15so8454962pgt.7 for ; Sat, 02 Nov 2019 10:30:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataegret-com.20150623.gappssmtp.com; s=20150623; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=b/9v9RCcZEmNajol9jHDCDQLzxQXpjAgX70Hd67ji90=; b=b/v4Hgbejrd87zUps/L4Y+a2UQZ3G9YTkGLC0fWnhhEGx79H2ktksN0vpYZhJjGTfl gXjZx4l0M0Osba5PzeeLaUNEtZ/9OwWeRqaBf1DjprzCSgaCG3Za118c+baLT4aNLf5z vbjMdoxqDIFuXi/Ql1puYzWrZjCsr5O0b8dpRKuspX40DPRWvWEESW5DmznC+tHolotf HbDoxmEcWKvHsgjDe1evXknM3DqFUTb1XNmutCu/DfAmDIczh39d97DjOoaQRm73jegN EOtoa0zoHO56/wDrNZUVi7MyP3T57xZn9k578CoPpeADewzCJN1VqWpg7iiSAcgqz5wq ntpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=b/9v9RCcZEmNajol9jHDCDQLzxQXpjAgX70Hd67ji90=; b=eujRAijE2NwIYgYWEibgi4jDA5691XvF5dvYj4FAZS0lTaVLTpOxxft3WX8Fv5Cx64 63Hf/WrnrB3YyXrSp+rleSS0k20rFMGfX9RbzW9mJxl5HyPFdwGee72xgd2g0m6az5md Q8b6R5Ac3ztylXFb5D3YyWg+JUz8uUprWWMC/vPItl63gzWORDBafKL1fZPRTvCEK6aY CFTxvcsbW0sqEmi2g034wHkfn+JDDVdAlLLXRnqVsU2RdEacqcdq8DhprTogTzBwk4DQ IhpY1VTGl9g8ZlRYKJB905W4ZxUUemSicEcKylslmpyU9CAwfa84/47vbdHtKefHLJXz zKRA== X-Gm-Message-State: APjAAAWPBLzWKRqrD+oetM775NMSBXXCyiDoiUrd3LIoOkhxY51lx2+g cPbiPOiQS4b7zDHTy8+eIywkVkTcNH8= X-Google-Smtp-Source: APXvYqwt9IjVuqBEx1KL08YRt9mtVuZMYBG6QXG8yM0f6DqJM/PB3j8M1t3P9SBCa3PV7J5vDb5gpQ== X-Received: by 2002:a17:90a:c086:: with SMTP id o6mr15038805pjs.37.1572715855102; Sat, 02 Nov 2019 10:30:55 -0700 (PDT) Received: from iMac.local ([213.87.225.210]) by smtp.googlemail.com with ESMTPSA id 13sm11618702pgm.76.2019.11.02.10.30.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Nov 2019 10:30:54 -0700 (PDT) Message-ID: <5DBDBD45.1020406@dataegret.com> Date: Sat, 02 Nov 2019 23:30:45 +0600 From: Alexey Ermakov User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Tom Lane CC: Sergei Kornilov , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table References: <16016-ed0345229ddc484c@postgresql.org> <158201568991600@myt5-2a1eccb4c218.qloud-c.yandex.net> <21601.1569179167@sss.pgh.pa.us> <5DBBF7B5.6040002@dataegret.com> <30149.1572707406@sss.pgh.pa.us> In-Reply-To: <30149.1572707406@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 11/2/19 21:10, Tom Lane wrote: > This does not look like a deadlock: the startup process is just biding > its time until the standby delay timeout elapses, after which it's > gonna kill the conflicting queries. > > It is, perhaps, arguable that it's a damn bad idea to allow > max_standby_streaming_delay or max_standby_archive_delay to be > set to "forever". > > I agree, allowing max_standby_streaming_delay be set to -1 is perhaps not a good idea. there is although case when such setting could be used now, see "BUG #14044: Queries immediately conflict with recovery when recovery_min_apply_delay is used". [1] [1] https://postgr.es/m/20160324204550.2920.87946%40wrigleys.postgresql.org -- Alexey Ermakov