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 1rX0Cg-008G1D-7t for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Feb 2024 14:44:11 +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 1rX0Ce-00Dnoh-V1 for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Feb 2024 14:44:08 +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 1rX0Ce-00DnoY-I1 for pgsql-hackers@lists.postgresql.org; Mon, 05 Feb 2024 14:44:08 +0000 Received: from udcm-wwu2.uni-muenster.de ([128.176.118.28]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rX0CY-005ayQ-4i for pgsql-hackers@lists.postgresql.org; Mon, 05 Feb 2024 14:44:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uni-muenster.de; i=@uni-muenster.de; q=dns/txt; s=uniout; t=1707144243; x=1738680243; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=j4s2uVvBXPnMNlpMLF0aJOrxzRcFWtsA321aOx4Naxo=; b=DVmJZYFC8e43rVcM+h2+oCN5K9ob+gBLy895eyAUf7/pjBM6huYjz+n1 EeslrvZZZfq3T33e3B07akoDHgfS66bVHTFTimzrINvo5/U4uyaWKQwYE 4n/GC6yjjb7gCFIqSd0voXq4r1By/XkZMFoGGG2lrHu5MJ8vyHV1haJjZ sKDkBmt5ORbTkSnM+Iq1e4Yi/55Bn3Tc3M3yAjzviEItQlRNKKKv5Enp0 EmgvplY+ARQBS7IAfAptEGZ1u/8yf2NcYjZ6ED84rPdb2vAEmeGp2Beh7 Wippn7OMX6WWE2GmxIER9VzNYPcczuYNTFIyI9X28PWHZO2IuOlOvFOxY A==; X-CSE-ConnectionGUID: auegBKsQTzmbg2RDQ8garA== X-CSE-MsgGUID: N77Gmwe8SLmAs6bjp+/qLA== X-IronPort-AV: E=Sophos;i="6.05,245,1701126000"; d="scan'208";a="306275658" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 05 Feb 2024 15:43:58 +0100 Received: from [192.168.178.27] (dynamic-092-229-040-096.92.229.pool.telefonica.de [92.229.40.96]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id 2B6CB20ADF1A; Mon, 5 Feb 2024 15:43:56 +0100 (CET) Message-ID: <48969cff-0a9a-448d-947a-e92898ccc57a@uni-muenster.de> Date: Mon, 5 Feb 2024 15:43:55 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Patch: Add parse_type Function Content-Language: en-US To: "David E. Wheeler" Cc: pgsql-hackers@lists.postgresql.org, Pavel Stehule References: From: Jim Jones In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 05.02.24 15:10, David E. Wheeler wrote: > Excellent, thank you very much! Updated patch attached. > > Best, > > David v2 no longer crashes with a null parameter. docs and regress tests were updated accordingly. patch no longer applies cleanly (tiny little indentation issue): /home/jim/Downloads/v2-0001-Add-parse_type-SQL-function.patch:140: indent with spaces.         PG_RETURN_NULL(); warning: 1 line adds whitespace errors. I read the comments again, and something is not entirely clear to me. Line 494 says "Raises an error on an invalid type." and 501 says "Returns NULL for an invalid type." Perhaps merging both comment blocks and rephrasing these sentences would make things clearer? -- Jim