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 1psyEK-0002lH-WF for pgsql-bugs@arkaria.postgresql.org; Sun, 30 Apr 2023 04:00:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1psyEJ-0004Oh-Mb for pgsql-bugs@arkaria.postgresql.org; Sun, 30 Apr 2023 04:00:07 +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 1psyEJ-0004OY-Bf for pgsql-bugs@lists.postgresql.org; Sun, 30 Apr 2023 04:00:07 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1psyEH-002ddU-11 for pgsql-bugs@lists.postgresql.org; Sun, 30 Apr 2023 04:00:06 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2ab25e8a4a7so12065371fa.3 for ; Sat, 29 Apr 2023 21:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682827203; x=1685419203; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=wBDl3DNm29BKETOeF3iYc+GkfWxz1+skCogHOZkXYqE=; b=BBol+b5Wjp5xaBH1hdNdOvX4+S3UpmtOte1AbshG3Yi7zhpyTZV39QbH5kGpy3O6lK ZEEG0Evu2Z/pLXQsgdoKIBfQg2M37JzbAIraCmFSvke6JWRMEO/DNdCFcpcIUmSbVGT3 W9d/sMeNsWCMpvfx41qogpWVtcsj5bTp2USpDOr6RjfiEQoOJG7dek18nhQe9lztnuiC z2tm0BEWa3CYxlOAIsSX0OUUvI3SNpzFbyGVyw7tczsk3fRqwdLExZWqTwQB1aCXCzRD AwwiMUeYb0XrhPoxDYihXbAnfqYeXSKakuu7z5xr6I6OxrRrAjkNOqcYsD/Kocvvg200 mPpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682827203; x=1685419203; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wBDl3DNm29BKETOeF3iYc+GkfWxz1+skCogHOZkXYqE=; b=YIQ1/W0tYLQ3Svpmt8e/+CP72cmH7elWl0NzuUxeLcxkQ+9pewQTCqTGfnnG65qKSJ z67kj2zu5B7q/hDouISPWL3zli5i3qakjFG4PtxzJOYtocfH2N9uV47VjgsgeZzXd5dA Rc2sd43PbCIUUs0/uJflrzpTRWLm6uiMwZF/vadbTCM+P8hgtAK9Nzt4ffc8wZ5rxrCl tbuHhW5kLcsqe08swV4QlFmOelWOSGFXVLPmbiw99NYWwL5UVsNFRZASVzGULUvhAJ+t R+KSFMmcalkwjz1Ka4I1zJrcmujjjKmp/IsYEE4tHpfUtDscB8nf4gfsUh5NYzt1G7J/ BuNA== X-Gm-Message-State: AC+VfDxluq+ncdKTfuu42UtCahoYUMQhBOT2hIh8e1uvIlTGnfqjrMuA lDn/K8aNJAdnBl29fx0iQboB1UO5zO0= X-Google-Smtp-Source: ACHHUZ4CBfJlmEvBs6eFTW3KzShT1TbvVXFyYJLJFiiZCHj/xZnRACttI+Mrgffiif2vhsxFAoInQA== X-Received: by 2002:a2e:9dc6:0:b0:2a8:c32d:1238 with SMTP id x6-20020a2e9dc6000000b002a8c32d1238mr2930189ljj.15.1682827202558; Sat, 29 Apr 2023 21:00:02 -0700 (PDT) Received: from [1.0.0.7] ([178.155.28.115]) by smtp.gmail.com with ESMTPSA id u20-20020a2ea174000000b002a784085edbsm3999417ljl.99.2023.04.29.21.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 29 Apr 2023 21:00:01 -0700 (PDT) Message-ID: Date: Sun, 30 Apr 2023 07:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array Content-Language: en-US To: Tom Lane Cc: pgsql-bugs@lists.postgresql.org References: <17912-82ceed78731d9cdc@postgresql.org> <1392974.1682694846@sss.pgh.pa.us> <1440309.1682705916@sss.pgh.pa.us> <1483429.1682709429@sss.pgh.pa.us> <5ebae5e4-d401-fadf-8585-ac3eaf53219c@gmail.com> <1805878.1682788590@sss.pgh.pa.us> From: Alexander Lakhin In-Reply-To: <1805878.1682788590@sss.pgh.pa.us> 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 29.04.2023 20:16, Tom Lane wrote: >> I suppose that waiting for v17 is preferable if the patch is considered as >> bringing a new feature (it's not the case) or could require extra time to >> stabilize. But I'm afraid that anomalies, that would require additional >> fixes for the change stabilization, could be related to the existing >> code, and thus that extra time will be invested in improving v16- too. > I'm a little uncomfortable with changing the semantics of non-failing > cases in the back branches. I agree that we shouldn't introduce a new behavior in the released branches. For that moment I was thinking about the choice between v16 and v17 for that patch to be committed to. But as you see the better solution now, the patch will be different and more extensive, I suppose, so I'd vote for postponing it for v17. Best regards, Alexander