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 1tRPV0-009MdA-Vk for pgsql-general@arkaria.postgresql.org; Sat, 28 Dec 2024 05:36:31 +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 1tRPU1-00FmNz-58 for pgsql-general@arkaria.postgresql.org; Sat, 28 Dec 2024 05:35:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tRPU0-00FmNq-OU for pgsql-general@lists.postgresql.org; Sat, 28 Dec 2024 05:35:28 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tRPTx-001zUs-0d for pgsql-general@lists.postgresql.org; Sat, 28 Dec 2024 05:35:27 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-e387ad7abdaso10383910276.0 for ; Fri, 27 Dec 2024 21:35:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1735364123; x=1735968923; 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=ZRgizZqq3y5Wkg/WQeFRja833GT5Ai2sPEHPVpGUWb8=; b=m0hR8IwacCWwVa75Y8YjO94VKVIBf0UyJGJ36nQ8jNayNrO98qGa8kydWBABu8QF12 xJltUFRI8EVXQX2O6z2hkmw4StPse75vFFcFNhhI6ErCHozo/mUxxR2fGitXFBhmBX0M Thf33h/hlZYyQtjxKA3mqMYnu8EwyZI0pRgQtTGOVDTqynGoynNDz4/Wg7NgYTgCaxb5 ggGakTs07i4Wy4bRKY2SypgzPlhjqJvttwBqQ8qzTarPGZbT2j+HkhkJAjpDtFNyz7/5 QI8GaeN1127yB2vLtWflyL47JC7tMkHOyo7u3P85v10wxDg2yJNm2G75nU6Kp8AwflBP 6nMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735364123; x=1735968923; 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=ZRgizZqq3y5Wkg/WQeFRja833GT5Ai2sPEHPVpGUWb8=; b=pAv0h+rlrqon3KcJweNmEBPYJAUjYSFnwBu7oSdmKAER2t9ivB0yVseIFtD9Dcw2Qx HOGX+6n8y1qRArQHQE7MnJJUn0r2uxIycLu+ue0GIkVoSLtt3wi4jQYZoywxFVRp/Pu9 MCSQEaMpT37EU67/ifQ2DSiokC7aSQ0O2dYabXu+uz07IDvH4TFLq3N3ObuinrBKVZAm PLCBxeY6MVqnQwkz4sWL5tTQkmiIrvy47+IF8IlajA5A+gJi6MDV69Ym+h5rGqCv/1ZU 1m6+OjV14LcRC29JgUzQQs9EWk/YfPaK22f87bqZZ7TitmrOCWi0LSyn1iOWaOESuKUZ MWhw== X-Forwarded-Encrypted: i=1; AJvYcCWTkDuUX2gCCJ1QLCQUDqjY9PQxpdJj2EyzMr8+KDUuuxa/hZvwlDafDeQRZUnM+ZKJBgkCkCzj2GmtiBgd@lists.postgresql.org X-Gm-Message-State: AOJu0YxppAEMfNIeePJ+XCEqqQbE/Z0t5TTFVuTjnIMu1BBI6x8EZxEk Pzq5aq6AbddN5fKdvbbhjtX32YSLcqL1noUvQEFhW31jSSs/8ysf79ZQU6dWymOAR2++Ilr9rr5 Jd7Kp2bqIorJz6UgTSEiJ3qynN6c= X-Gm-Gg: ASbGncvMGuMaS220adBL9AJ1+n39td58QucpRmrMF1549U7+ZwI+BBcYprAs4ZvOO5Y 8uCKS1R5qvvmz0W1gYX/CVdatLuddvWlRNNiXGg== X-Google-Smtp-Source: AGHT+IEBuyb08ApOcOXP9HTl8i600T0hVw0WVAABunnz+tZrLozduy42lrh0xGYIME4Gn7PhbcMedP6CAIg3H+ayKbo= X-Received: by 2002:a05:690c:6901:b0:6ef:4696:f1cc with SMTP id 00721157ae682-6f3f8136700mr232768847b3.22.1735364123012; Fri, 27 Dec 2024 21:35:23 -0800 (PST) MIME-Version: 1.0 References: <20241227205025.1d059f72c7c08d23c9648c26@magnetkern.de> <20241228004009.267f21b78394c934f27f9974@magnetkern.de> In-Reply-To: <20241228004009.267f21b78394c934f27f9974@magnetkern.de> From: Pavel Stehule Date: Sat, 28 Dec 2024 06:34:46 +0100 Message-ID: Subject: Re: search_path for PL/pgSQL functions partially cached? To: Jan Behrens Cc: "David G. Johnston" , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000001bb4a1062a4df2d6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001bb4a1062a4df2d6 Content-Type: text/plain; charset="UTF-8" Hi > Maybe not many people run into these issues because schemas and > functions aren't used as often in combination? > I think schema and functions are common combinations. But when people have objects with the same name, then they are careful to be sure, so objects have really identical structure. Using different types in these objects is very rare. And because Postgres doesn't support it well, experienced developers don't use it. Similar issues can do some issues after an stored procedures update, because can require session reset. Or when you need it, you can use a much more dynamic type like record. > Kind Regards > Jan Behrens > > > --0000000000001bb4a1062a4df2d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi


Maybe not many people run into these issues because schemas and
functions aren't used as often in combination?
I think schema and functions are common combinations. But when = people have objects with the same name, then they are careful to be sure, s= o objects have really identical structure.
Using different types = in these objects is very rare. And because Postgres doesn't support it = well, experienced developers don't use it. Similar issues can do some i= ssues after an stored procedures update, because can require session reset.= Or when you need it, you can use a much more dynamic type like record.
=


Kind Regards
Jan Behrens


--0000000000001bb4a1062a4df2d6--