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 1pGNd6-00071i-UH for pgsql-general@arkaria.postgresql.org; Fri, 13 Jan 2023 17:14:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pGNd5-0004i8-Jo for pgsql-general@arkaria.postgresql.org; Fri, 13 Jan 2023 17:14:11 +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 1pGNd4-0004he-2P for pgsql-general@lists.postgresql.org; Fri, 13 Jan 2023 17:14:11 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pGNcz-0002h7-VT for pgsql-general@lists.postgresql.org; Fri, 13 Jan 2023 17:14:09 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id B9AA33200918; Fri, 13 Jan 2023 12:14:01 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 13 Jan 2023 12:14:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding: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=fm2; t=1673630041; x= 1673716441; bh=eSZxGpJBtrg0qlb+YTCSxzAOW+LHsM2i5QaOPt3XshA=; b=W 0T/Zom+YyJVoTjTqb16l3MMy0Jrw8cXxoY87bMWx9rf0c+5xt48ylf23qTKI/Hxn Ln4wwdzAR00PJKw4F7J2mFrriypmwaOdzpaE8gojPSSfVoHq1RnqhLhhZqdoKjET bLsVsXdWBrOd0WMRRhucDUqFglWQexdthVx8/mqLQI3+KknzmWZlZOwQFxD7Zp/L W/4f1Sq630tMCfu2+MiGiOoIOnS5cw1R6p74GwDnJ7Z+KBxihMvSqDd6etA0bj8o 1e/uWcYlKuNi4xeCH0Lk6Wp3AsjOb8YnKvlKq+B7vn+ENuzrxYR6+E5KVOVXB+jr Fv9yVX1tpdoTz+69sKmLw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=fm3; t=1673630041; x= 1673716441; bh=eSZxGpJBtrg0qlb+YTCSxzAOW+LHsM2i5QaOPt3XshA=; b=S 9NS7tWZJxExnjJEUMlbcX6Mbn7DMzdRv7XeE8cb1/IR69fhDKpQaLFRsegAiAQqs BBsXFZZi/HEC/U4Mxsj5WTpXSO1oYVi9ha6qs7h2N3UxmtgcpT+9PT2Tozy7vbnN bK541ZU/XY8uvYsL0mki4Ud9wth14PKUFBL7SF98sHXETeWqamHgvqEBcRRwGsP6 OoJPSFhUYcg6HElTwj94jmKKFuEcNHPPMLglgVowoU/pYfjl0bkizaNxTub6RyPE OO2ZocK5toYcc3feJLB6v9dU0YZ7kkiCRUuVVBF8NGnA5Ezx9FjQdZ8K5El/Ynq5 zEyQm8ggJ8kKZfHC9rrGg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrleekgdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthekredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeehudfgtefhtedtheeiveetueektdejvdfhveekgfdu feegveetuddvuedvgeeggeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 13 Jan 2023 12:14:00 -0500 (EST) Message-ID: Date: Fri, 13 Jan 2023 09:13:59 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Directly embedding a psql SET variable inside another string? Content-Language: en-US To: Adam Scott , Ron Cc: "pgsql-general@lists.postgresql.org" References: 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 1/13/23 09:08, Adam Scott wrote: > Do you mean like this? > > postgres=# \set v_embed %:v_ssn% > postgres=# \echo :v_embed > %345% > postgres=#  SELECT * FROM employee WHERE ssn LIKE :'v_embed'; >     ssn    |   name > -----------+---------- >  123456789 | John Doe > (1 row) > > Actually that replicates what Ron got to work. What Ron is looking for is to skip the intermediate step and do: \set v_ssn 345 SELECT * FROM employee WHERE ssn LIKE :'%v_ssn%'; -- Adrian Klaver adrian.klaver@aklaver.com