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 1qIwaC-0000yG-Q8 for pgsql-general@arkaria.postgresql.org; Mon, 10 Jul 2023 19:30:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qIwaA-0007v0-Q0 for pgsql-general@arkaria.postgresql.org; Mon, 10 Jul 2023 19:30:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qIwa9-0007ub-W4 for pgsql-general@lists.postgresql.org; Mon, 10 Jul 2023 19:30:02 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qIwa1-003KqQ-UX for pgsql-general@lists.postgresql.org; Mon, 10 Jul 2023 19:30:01 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 26CB63200942; Mon, 10 Jul 2023 15:29:50 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 10 Jul 2023 15:29:50 -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:sender:subject:subject:to:to; s=fm1; t= 1689017389; x=1689103789; bh=LmFG7otifDRK6vnZ66ZlroMhXFhyFZ3pOKS a7EzmoSc=; b=sqp3+ijLQN+D0hEM4Sxi6fyKQn9JLCCkG+ERpBhH9NrwGhEYMNv bHAwQ8+Q1cZwdHys2nEO+hb2KD0iwvFIjTOPHEH6FoCnCmarV5NOF5LvASF1pkvQ RYFC/W/yGt6zM1skmmmlZf047wtqSkS0W1JGcXqPFVrh9ez/kCaqoEvLuPRedADQ SRz2Dr6AlGXN2XWT1WGdIR1Eg0PqX4dY9/2xDo6J16ABB6Rd6ry19ShPHzZUk0Cj IDnSQw9HLZhyF/hp0A0m3SBKYGcX3h4S9hbuvKZtbENVSHHL/m84cjCmQf5HPU7F mn81A6hXnLwJCLYC54DLamiTLo95qCk75pg== 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:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1689017389; x=1689103789; bh=LmFG7otifDRK6vnZ66ZlroMhXFhyFZ3pOKS a7EzmoSc=; b=oKLgqqdMPs1CIL2wkzTHINDNfyl6jZrpvkaHuzMdshd4r7rAR3d kFK48Bh4raj4Mtub2a2dtvd6P5hbrI7wNhfDRqTxtd4zOtqE9pKDErANKyL8udob dLgfAM/5iHmsXKP2xc3zfl6f5Cf1x0ideGHTmUYHPuCH565hqBwUKQkLorHFxh3o EnVIl8Qk+EzOdpLz264bUcp+p5Qz7k9CJWmk9tYZV3BVuHLXY3v0Ow0Qpylc7Nt9 kXHfwxKzUqipnNOpQqbquKtZ9nRfOFMbbLvh9kf5fhf3o+RFdUuZfdyPGe95QH9N v2qN0MdMooHpqVfKAMe60kUPBnMyLzGig3w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrvdekgddufedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnheptdfgvdfgieekfedtvdffkeevgffgvefggfehleei ledtjeffffffhefgffehvdffnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 10 Jul 2023 15:29:48 -0400 (EDT) Message-ID: <26cb1164-defa-3a84-b2b2-fe22092d9654@aklaver.com> Date: Mon, 10 Jul 2023 12:29:47 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: Using "exit" to bring "goto" functionality. To: DAVID ROTH , Christophe Pettus , Bryn Llewellyn Cc: pgsql-general list References: <655E5E21-FCED-405F-81F6-AE2713F27337@yugabyte.com> <39EC45EE-8162-4B19-97C2-BE54E758B294@thebuild.com> <417293360.172884.1689016086131@connect.xfinity.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <417293360.172884.1689016086131@connect.xfinity.com> 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 On 7/10/23 12:08, DAVID ROTH wrote: > I am a newbe at my current job. > They have a separate log table for every table because they want all the columns. > I have been looking for a way to go to a common log table without requiring major changes to the application. > > With your help, I have a proof of principle that I can demonstrate now. FYI, you replied to the wrong thread. > > > >> On 07/10/2023 2:58 PM EDT Christophe Pettus wrote: >> >> >>> On Jul 10, 2023, at 11:54, Bryn Llewellyn wrote: >>> >>> What is the rationale for supporting what seems to be on its face this strange functionality? >> >> It allows you to EXIT or CONTINUE a loop thaIt is not the innermost one, by naming the label of an outer loop. >> >> One can debate endlessly whether it's good or bad to include that functionality, but it definitely has use cases. I would assume that at this point, it's not going anywhere. >> >> The relevant documentation is here: >> >> https://www.postgresql.org/docs/15/plpgsql-control-structures.html#PLPGSQL-CONTROL-STRUCTURES-LOOPS > > -- Adrian Klaver adrian.klaver@aklaver.com