Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thZji-00490a-PK for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 19:46:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1thZjh-0043VA-5S for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 19:46:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thZjg-0043V2-R3 for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 19:46:28 +0000 Received: from mail-oa1-x29.google.com ([2001:4860:4864:20::29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1thZjd-0005pL-2N for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 19:46:28 +0000 Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-2b832eab8cdso2261276fac.0 for ; Mon, 10 Feb 2025 11:46:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739216784; x=1739821584; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=DFLmJkOTTLXY/IexEkty9Q+KUxLJSGqHFTvxBbQ82Uc=; b=cGOZBCffj/ztl3IlKCX74mEbMmlhjvE5/On1dU8WkyewdZQrlmqShepiksja4lIGTT vgyFo7U/SwLTLsFLDJPEuXJJHpT4bj2o7MMbdtTRRVGq9tJdX9Pp2t0CWVXYl42/Rj61 0Kd3QBPzewZq1gz9A/VlyRYBrkX/TUom37LVZg2660vsX/1M1e3mCWPS+i4kLN7L5Yox 4GGgH93a3AnRnnvDGvZZzcPRJycO/XaRu5bkQk0YDVEnaZQUHaV0Rf89CM6sQZghTxKI tp6qpy/9O0U4zDpEXFFwb3ZA1YTU4ZO2VqpZe8bRQ80K74VMHOiaC32COK/rCLNW3qGk FeEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739216784; x=1739821584; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DFLmJkOTTLXY/IexEkty9Q+KUxLJSGqHFTvxBbQ82Uc=; b=D39YsrTifmq/VB4XTzdYx6JM3MEE3Q/166j+A5bthDoRTHOIjARNg1VnJg/P32MhCQ ELTRW+lM5U113xvWaMDZKfpMys6fTC/y6alf0DH9T99+YGN5t8irxsIb8Hi+gMHSqpkg 18+IS5C7naaJNfuS25eudi2tWFl49YITyrC63g9X00QSEc30A3/9L0mWngqdMBjLIDjF sgrYwLr18qMZNPCHPnvU5zVCUkncdH2YD5nSpAPlydMuWr6SXNoGksSaYoNENTwWV3Ly b3JBUyqTt5IgEPSodzVpt/FOcwcXy6SL1P8rUapNaCRaCcTpXpa8JL5ULOutpL7h2hAV tfBg== X-Gm-Message-State: AOJu0YwLbMH049gl033qr1CG2RxnwvdBz5e0LG/yI09iLfCLr1ndMmiQ 1os0eu4NOEEMsiJTcavj9pnFKNlQrq2kiDffNpAVC4kVOecQmVKXhNRMk1kB0/yXdVhOhAgGDEd 6/eBsH6Z3O5zTbnSIXCv2X568WfnrcQ2B X-Gm-Gg: ASbGncsr+Kb2PvaS2hen7F6QbFFyOuVbXgxunQ9roL1EU42ze+OJE9o+IBpv7CR8d0I vJQ6hHLsS6eh3Ur4BAtt+pqkE/ETsLkfH2xsGJRZUuZDWzYyI2Tv1Ib2pd506c1rSHXF1qu8ok+ hE2UT32PZHVk5D X-Google-Smtp-Source: AGHT+IFfoRMZj516LtV8nitrcdBKGd2CnWxrt58i9XPdxjdpds7ZWc981KdAtevEWKfSKCGGQwPIo1YzF/51J6tMMog= X-Received: by 2002:a05:6871:60b:b0:29e:290f:7af4 with SMTP id 586e51a60fabf-2b8b59a9957mr612157fac.34.1739216783819; Mon, 10 Feb 2025 11:46:23 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= Date: Mon, 10 Feb 2025 20:45:47 +0100 X-Gm-Features: AWEUYZkr9X0CL_XYBpScXech5dABcOL0Y6EV3rtzxH6nP3hlr6I1ld3GX9mFkBA Message-ID: Subject: Any plan for minor release? To: pgsql-general Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, is there any plan for another minor release? I'm facing troubles with some queries on PostgreSQL 17 and 16 blocking upgrades causing "wrong varnullingrels" error. Per our conversation in CSPUG (Czech language, https://groups.google.com/g/postgresql-cz/c/_jah9d1U1R8/m/HBJszs-2AwAJ) we have found out problem is fixed in both REL_16_STABLE and REL_17_STABLE branches, not present in latest PostgreSQL 15 release and also fixed in current master. Last release (https://www.postgresql.org/about/news/postgresql-172-166-1510-1415-1318-and-1222-released-2965/) happened at 2024-11-21. Is there any schedule I can follow or anything I can help with to make a new release happen? Our apps work well with both REL_16_STABLE and REL_17_STABLE checking via our app automated test suite.