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 1rNGzy-00AbFZ-BS for pgsql-sql@arkaria.postgresql.org; Tue, 09 Jan 2024 18:38:50 +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 1rNGzw-00ExHW-3V for pgsql-sql@arkaria.postgresql.org; Tue, 09 Jan 2024 18:38:48 +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 1rNGzv-00ExHN-RA for pgsql-sql@lists.postgresql.org; Tue, 09 Jan 2024 18:38:47 +0000 Received: from mail-oa1-x31.google.com ([2001:4860:4864:20::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rNGzs-000hLM-GH for pgsql-sql@lists.postgresql.org; Tue, 09 Jan 2024 18:38:46 +0000 Received: by mail-oa1-x31.google.com with SMTP id 586e51a60fabf-2043e721daaso2258255fac.2 for ; Tue, 09 Jan 2024 10:38:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704825522; x=1705430322; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=s5gc7cAVA11pNJrSGLdwd4Gxl570Y9nrW9CNLJH2V7E=; b=OthOHqOHm2SenpJALr5nRm90bt9XlHcQzrssQjLzgulTgEd62J7kUP6eq962GnRWrr 4QLofUBq7SEh7zzpDpt8Cnq/VMIiiooyGFBhyhToAwSkr7Ux5G/wlT2nRb/1Ag+2UC+X DIIF3/9pmPssvjVI6xxTmoxkY2DqkshYqXWJ21f8pzluFpqO+onwbIB0UPGpJvoRug1T phi0XBeCfQfrAHCHVg7Em3tuckz05Sl1ctmvMqmhMJoewpmRvu4SytWCP+5vUE603SyI 4rR6pH5j+OawYkvxmbKXLlPl+R1wKWzBUjsllNJvsjwmOVSQNq6i8v+zr7syJRm3dtPj XqkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704825522; x=1705430322; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=s5gc7cAVA11pNJrSGLdwd4Gxl570Y9nrW9CNLJH2V7E=; b=RmFTpvBc/rihNUXxHCIHRg3rsmzn2qBA5xvpXouCvonM9Ju9vOeeIjvMvEInF4Jizt Xrye3BEpZKLkKChWZD/ri7kKzBSdaGu2CHYOJcJx31NJIv9fHh+TRzmE6ddStUyRrJIl WBS4Cq4bzeEaG7Qdu7limjsCbctYUTLqXUzF3oCgqAu53S/xKkTxPLvm1rtHn9DV3tno RYOfN6fGe9Wovnxnfj8Z9nWpys8K6pAHaGSVKQwJqRv3oH3wVhJXpIhQoqGsP95lVIyN 0sYvUtnjA+40jUcJV5Os0ABQx4iSDtNHV7CVtT+Mk3+ZZ60jVFPCJNuzKJzTulUnF7+b x7AA== X-Gm-Message-State: AOJu0YxXx/I4Bf7RvKnHrH+YhoeCJ02ADD5bCgbFwaL9yQnQ9hzfYvpB OQq1PNrTBYvHBwZPRVlbLEOJn9jUrwGVIqQyTPc= X-Google-Smtp-Source: AGHT+IEr59G3PsIP9/I0+VH4k159M9SsE4toiTRTvhMwPrWAZOxv44EbZPz9Yxe0AZtN+IbpM5LPqCRaPGs6caSbWqI= X-Received: by 2002:a05:6870:6f11:b0:202:ffc8:c6bb with SMTP id qw17-20020a0568706f1100b00202ffc8c6bbmr6943377oab.4.1704825522153; Tue, 09 Jan 2024 10:38:42 -0800 (PST) MIME-Version: 1.0 References: <5d61c61ce2574b969895d5a4b6ba2602@express-scripts.com> In-Reply-To: From: "David G. Johnston" Date: Tue, 9 Jan 2024 11:38:31 -0700 Message-ID: Subject: Re: How to use one function which can be accessed for all schemas To: Bindra Bambharoliya Cc: "Wetmore, Matthew (CTR)" , intmail01 , pgsql-sql@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000a6ef1d060e879fe3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a6ef1d060e879fe3 Content-Type: text/plain; charset="UTF-8" On Tue, Jan 9, 2024, 11:09 Bindra Bambharoliya < bindra.bambharoliya@gmail.com> wrote: > Create function in public or catalog schema. This function will be visible > to each schema and user > Schemas don't have their own visibility, you should not create stuff in pg_catalog, and public is not guaranteed to be in the search_path. And, please do not top-post replies. David J. --000000000000a6ef1d060e879fe3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



On Tue, Jan 9, 2024, 11:09= Bindra Bambharoliya <b= indra.bambharoliya@gmail.com> wrote:
Create function in public or catalog schema. Thi= s function will be visible to each schema and user
=

Schemas don't have = their own visibility, you should not create stuff in pg_catalog, and public= is not guaranteed to be in the search_path.


And, please do not top-pos= t replies.

David J.


=
--000000000000a6ef1d060e879fe3--