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 1pomLe-0006cl-No for pgsql-general@arkaria.postgresql.org; Tue, 18 Apr 2023 14:30:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pomLd-0004aq-J1 for pgsql-general@arkaria.postgresql.org; Tue, 18 Apr 2023 14:30:21 +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 1pomLb-0004ah-Vj for pgsql-general@lists.postgresql.org; Tue, 18 Apr 2023 14:30:21 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pomLX-000Vz9-5B for pgsql-general@lists.postgresql.org; Tue, 18 Apr 2023 14:30:18 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5AAE65C0167; Tue, 18 Apr 2023 10:30:13 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 18 Apr 2023 10:30:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1681828213; x=1681914613; bh=UZGiAX778fdeaJd31e/RREcJTLaK4mG9Beu 4C7rKaTg=; b=BDUTUvaDGeSW1bfMtjt9Mwvzbohb8JFOfeM+mAFpdRphQdLGvSR LsqK6c0JPT5ZhlVja2zMC65hLCKFdsRgpfCDVQ72zAq0MSY8z9fmVbQPm4up+phY LBS1I7Bzi/u8YpfdHaGXsMNeLS3Kr6PKM6E/ZcWFrpiMPgdonuRaHlFYJJNRTrng lUzUhR+vpsUiippAw12FABCxzDekgNt3O3ZwWyYAFW2F86vaYnQ+jvMnex6Vt8A0 S6bAZuEaBwqj4JC71S2WOxve7nQtTp4dSu3/Yl9T1DVANi5TW8RhFUrrYj0C2rYA JHklOe08pI7u5jTBMxGaVQ/9eGjMM4qrSAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1681828213; x= 1681914613; bh=UZGiAX778fdeaJd31e/RREcJTLaK4mG9Beu4C7rKaTg=; b=V Xc4X80wGhk8ULyJ1F+QEyXeay/vn8TA2Q1fY8orBZfVZRL+Q+SohMVgq9XMD105k nxgsMLAJf9qGVW/brBwv58jParJ23WteFQFvHmucrg7KrQSnN4IR63OO/hYn7bus rkVHMVU3vYYJ6/WNQWcSOnndFfgeNGDoWyAl7ARd6sFQj0IjzVAZC+JTvlnq2cmh WNpjise+8vJwo8dMZObMxNvLcLXE7lf48AFkLsTtgQ2wnBn5YwEnsjAiaEqVPdt4 n/JLTaOnUqVwbS0wArSPktzoI4Wy4PE0rr+drBsrPzH+IOWDmUJGeQ0UYt4wlIbg NmjJOnAlS0yIT6n+44igA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdelkedgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeffudehtddugefgkeevudffheevvefhfeettdfhveei vdfgieeghfeiueeggffggeenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 Apr 2023 10:30:12 -0400 (EDT) Message-ID: Date: Tue, 18 Apr 2023 07:30:11 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Request for information about postgres version 15.2 stability To: gayathri ramesh <17gayathriramesh@gmail.com>, pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/17/23 23:56, gayathri ramesh wrote: > Hi Team, > > Our company is currently supporting around 100+ postgres databases and > we are planning to upgrade to version 15.2. We want to ensure that there > are no major critical bugs that could impact our production systems. > > I would appreciate if you could provide us with information about the > stability of postgres version 15.2. We are particularly interested in > knowing if there are any known critical bugs or issues that could > potentially impact the system. https://www.postgresql.org/docs/current/release-15-2.html > > Thanks in advance. looking forward to hearing from you. > > Best Regards. -- Adrian Klaver adrian.klaver@aklaver.com