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 1qJJnh-0002XC-LW for pgsql-general@arkaria.postgresql.org; Tue, 11 Jul 2023 20:17:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qJJnf-0004HO-3F for pgsql-general@arkaria.postgresql.org; Tue, 11 Jul 2023 20:17:31 +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 1qJJnd-0004HE-W3 for pgsql-general@lists.postgresql.org; Tue, 11 Jul 2023 20:17:30 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qJJnV-003XFM-Lc for pgsql-general@lists.postgresql.org; Tue, 11 Jul 2023 20:17:29 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id E1B613200917; Tue, 11 Jul 2023 16:17:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 11 Jul 2023 16:17:19 -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= 1689106638; x=1689193038; bh=YPR4OaVS9X2dH/MNEFnpPpKWd8P1laOqChL VdQ4xNdE=; b=gIzwkxSqfw58dLuWFC3sDjWMaUx0MF49mdAGG+GCx+BPyaTW7jG tJ+FciXQRONpU/lR0m69RSwbX+7yiWB1ClKPPuZ22Hst/3ys97XdhVomp3+nT3rJ z2oLzD6RiJYquq5XcSls9Hs625IIWJBYaDfj0ysZfj2aIMa+YMbpdHK7CDbO5a/t 77R39+VcLSJCOOt+J8K7lci+h45IMC4ZfKPtEIWNJhdUVcG3B2GQPXWHJkaA2noB c+9ee3H304W4/q9nWwwIGX3s1cXFbaHBVJN4I5UonsdnERoN7ZTvfQZBQKznPQlK E31vmXhzZVnpx7cg+g3Pi1nrOLPKz3NrHZA== 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= 1689106638; x=1689193038; bh=YPR4OaVS9X2dH/MNEFnpPpKWd8P1laOqChL VdQ4xNdE=; b=mZnIweilUwSLanP2FKAvzClMNqY0qPLo2hyUvptYxBK76c97sa1 1qqRfyI47lbu41Vh9+TW7u3kv1FJCEqwOhWnLHRggT9j2RfK774ySYN/8revjW+K 19OSTOwxn82VzD6pxyKZLYTx1GPQtDJrGmy3wePvlxyoNVihXy+flc9Su4cr27z+ 0lQQOyIOm2ntaYZ2GY5nAsTTIx/C2qNMNY4wtgJyS3bcU56pvSRwQpi/wwxFzoj4 6//YtuhaQ0UVnkKflSIRoDA/gwaK0P69NoLHq0S+Rl7J0z3UL7Ym2q3FYnukbPnS 0kWEogHdOQB6ZWKAkQHDdU4bHFZkZwZLxRw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrfedtgddugeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepgfekvdegffegfedtvdeggfeutdeuueejtdegveej teeufedtvdduudeufeejgfehnecuffhomhgrihhnpehgohhoghhlvgdrtghomhenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdr khhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 11 Jul 2023 16:17:17 -0400 (EDT) Message-ID: Date: Tue, 11 Jul 2023 13:17:16 -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: How to add function schema in search_path in option definitio Content-Language: en-US To: Lorusso Domenico Cc: pgsql-general@lists.postgresql.org References: <9f3db764-804e-7154-3f8c-f5f19628178e@aklaver.com> <20230709110149.hdjv6vhukz2sz3c6@hjp.at> <87e07b97-fac2-7dae-4f7e-43e3d6cfb978@aklaver.com> 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/11/23 12:47, Lorusso Domenico wrote: > Adrian I have read your suggestions, but: > 1) I need to change path inside a group of function (like a package) not > for any connection > 2) Yes inside function is clear I can do that > 3) some like 1 and, moreover, I can't be sure to create my own role, > because the target db will be cloud sql First mention that you are using a fork of the community Postgres. In any case Cloud SQL does allow creating roles: https://cloud.google.com/sql/docs/postgres/users My guess though is you will need to do 2). > > My question doesn't aim just to fix a specific issue, but to learn the > best way (if exist) to solve the class of issues (raised by the case) in > postgresql. > -- Adrian Klaver adrian.klaver@aklaver.com