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 1n84Gw-0007sr-CE for pgsql-committers@arkaria.postgresql.org; Thu, 13 Jan 2022 17:52:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n84Gv-0004Ix-48 for pgsql-committers@arkaria.postgresql.org; Thu, 13 Jan 2022 17:52:25 +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 1n84Gu-0004Im-Ph for pgsql-committers@lists.postgresql.org; Thu, 13 Jan 2022 17:52:24 +0000 Received: from mail-wr1-x432.google.com ([2a00:1450:4864:20::432]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n84Gs-0006NB-1j for pgsql-committers@lists.postgresql.org; Thu, 13 Jan 2022 17:52:23 +0000 Received: by mail-wr1-x432.google.com with SMTP id o3so11522122wrh.10 for ; Thu, 13 Jan 2022 09:52:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:reply-to:to:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=GJf4tIYJVF/I9M0a80tLZn9SvZb/UPdRK65ovHIsm34=; b=EXfV6Ynv3BYCeq2oHiCFa4KVLZYOUziafetAmBDz8HA4TaY10qkATblzmIRE26lGPN LSI39DWs3TUHw1Kc8yYyjl7/YThdzWBrDCVlzWDnLTslL8+K5V3W2oENzYGO9EhTfg7+ JeFZ0p9Wm+n/SBTE19iy9QmEJd/5NnM/U5PRaGU8p5A86MsUWcyaYiYX8NHlLOE9Sx/L 7cu2nHsU4HTXgzskAm3qQyjGKl/dwPRfJCgmViZcKqiGjAlAIHIGZ8dhcFWypbqqBBBX 15Qhx+RliWGoh5C1DDVl4R52bdXxaXrfDjRQ6lzQqyp/jAvF+6AUgHfvQ79G/gSwA09z /I9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :in-reply-to:references:user-agent:mime-version :content-transfer-encoding; bh=GJf4tIYJVF/I9M0a80tLZn9SvZb/UPdRK65ovHIsm34=; b=ipVzQytNPd9XKKGcxs+GJ9DRAGg8Z4PgHk1a831ezomIcVpdmAMuktZSxVa03awlpP /vS89yYKBnOxFL1u6VQpWQkWNwmAiwv4z9YAtnjCeg/mYLHNJPXwVJ7lYzE9QII9er2W e2bBXY33e8U0stCnuFSjJds7lN/HUJnj6dWHb76hiU32DMrxd+c+7/0NYz0B2zdySFm7 7fPvkskNRj0ETKcU5AmhcsFycfXXEUcqpRIqSSGPy5whEDVG2CpRILMhYxLziDo0N3g6 CEHExiEUE8nk6/46500WSpulVb7am2aSyyLz7Vm1W4PoQvexvIyKfkGVlHvC4AlvOhHz hQRg== X-Gm-Message-State: AOAM531+kVMl7YnFYwuFc8uIv4gpF9tuKZz/JvITrJ+jWXK+bzSGRYlp S33uVruYW3lggB+RY0f9lzE+lk1ZtDfVSJTe X-Google-Smtp-Source: ABdhPJxqMHanmBgmfE6m1ER8mPBFffiDw/ei2wtolq5T1pLrLp+L60r54TQrDNxZuIOUbPbQSasmHg== X-Received: by 2002:adf:d219:: with SMTP id j25mr583681wrh.196.1642096340373; Thu, 13 Jan 2022 09:52:20 -0800 (PST) Received: from localhost.localdomain (dynamic-edxzkbgi36x9bhyfb-pd01.res.v6.highway.a1.net. [2001:871:5e:b726:b655:92b8:dc78:787]) by smtp.gmail.com with ESMTPSA id c7sm4318789wri.21.2022.01.13.09.52.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 13 Jan 2022 09:52:19 -0800 (PST) Message-ID: <9f0c0a96d28cf14fc87296bbe67061c14eb53ae8.camel@cybertec.at> Subject: Re: pgsql: Improve error handling of cryptohash computations From: Laurenz Albe Reply-To: pgsql-hackers@lists.postgresql.org To: Michael Paquier , pgsql-committers@lists.postgresql.org Date: Thu, 13 Jan 2022 18:52:19 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) 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 Tue, 2022-01-11 at 00:56 +0000, Michael Paquier wrote: > Improve error handling of cryptohash computations This commit changes the signature of the exported "pg_md5_hash" function, which breaks my extension that uses this function. Is there no way to avoid this API break in the back branches? Yours, Laurenz Albe