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 1sQTNq-009zt3-Ej for pgsql-general@arkaria.postgresql.org; Sun, 07 Jul 2024 15:00:58 +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 1sQTNp-00D9Y7-2I for pgsql-general@arkaria.postgresql.org; Sun, 07 Jul 2024 15:00:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQTNo-00D9Xy-O9 for pgsql-general@lists.postgresql.org; Sun, 07 Jul 2024 15:00:56 +0000 Received: from fhigh8-smtp.messagingengine.com ([103.168.172.159]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQTNm-000ry2-6i for pgsql-general@postgresql.org; Sun, 07 Jul 2024 15:00:55 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 6530711402F7; Sun, 7 Jul 2024 11:00:53 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 07 Jul 2024 11:00:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc: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:subject:subject:to:to; s=fm1; t=1720364453; x=1720450853; bh=vYx6hphaz3gp21wlrHODQv5j64U7U78KyZUhHE/EtgU=; b= vGRJW3gFq52j3gqS8BWynsKfSPZcn9xYZgKHhA4X7Oq2rz04MPu63SPU1jljZMhr gVpQDBrP1vDMohv1szUgPweJ5QzabHOM7a78p8eId3GI4AIyfMgvbBUB7gkBLpFi h4ZqTO6sKiTfnZkfd4C/q2uhMa4WcVZDm4T7hOb5yi4RHMvf88ZHKTVXCNiT02O/ 4g+5XInPPYmgFrBboU4lizjxXU0onBhDNcNR333/sEuXxZE+cmWmcGC0UXKuLXr1 FmHgLPMIhTRFzJDTnQjJTvaG3COONe+NwLdFHMQR7FoNg87biNHRsJzu0dB6nc79 mis7nvQvTpo9o/PdNMr/Mw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1720364453; x= 1720450853; bh=vYx6hphaz3gp21wlrHODQv5j64U7U78KyZUhHE/EtgU=; b=d Pao96bVTpiOSOlRfy6DcykSveMYbzVH4m2Jqvnn5f/lI9yHKkfGF6uUYvL8tZCPe 3di6RF87Gj3GzwYA598XT4eXJN4slOsu4NSwNQzTBkStAqNo7khVSAivQeGffAvf sBxgVhYBGMtvpM0HbqgtedoJZRwn8JT/SvB9Wx/x9EKUP03iZTK5MvUvxSOOzCht KJ/5hfsbdjcCg1iALlHFN5I3rlRXmNgGw/KMW6ikqy/JnXykWA/z+7dOUQv6i50U hNxf91JbOk3yTCZ9zIn4lo4GFpXe2eaxZ0pJLwirCuL1AyZLwWN+OnhRvhrJtjQh F059HOd775zC7jsfQOc8w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdehgdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeefgeefieeutdfggfetgefgheekjeehteeileeigfet ieekjedvieeviefgheevtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 7 Jul 2024 11:00:52 -0400 (EDT) Message-ID: Date: Sun, 7 Jul 2024 08:00:51 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Declaring a field that is also an out parameter in a function To: Pavel Stehule Cc: Michael Nolan , Tom Lane , "pgsql-general@postgresql.org" References: <577338.1720304029@sss.pgh.pa.us> <3f8781c5-d625-4f24-b96d-56a45a0dd257@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/7/24 07:53, Pavel Stehule wrote: > > > ne 7. 7. 2024 v 16:48 odesílatel Adrian Klaver > > napsal: > > On 7/7/24 07:42, Pavel Stehule wrote: > >     I'm not sure why there's a warning about using an alias. > 43.3.1 says > >     to use them for improved readability. > > > > > > it is obsolete - aliases were used when Postgres doesn't support > named > > arguments. > > Is that was what it was complaining about or the fact they where > declared and never used? > > > I am not sure if I understand the question. My  reply was related to > generic usage of aliases. The conversation was: Mike Nolan "I'm not sure why there's a warning about using an alias. 43.3.1 says to use them for improved readability." Pavel Stehule "it is obsolete - aliases were used when Postgres doesn't support named arguments." I was just trying to confirm that the warning was not for ALIAS being declared. That it was for what you state below. > > Report from plpgsql_check was correct - and related variables were not > used. > > > > > > I  don't know any good reason why one variable can use more than > one name. > > Section 43.3.2. ALIAS provides the pros/cons. > > > > > There can be an exception when argument names are very long, but > > generally they are not used. > > > > > > > >     Mike Nolan > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > -- Adrian Klaver adrian.klaver@aklaver.com