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 1qVv2Z-001aBS-RY for pgsql-general@arkaria.postgresql.org; Tue, 15 Aug 2023 14:29:00 +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 1qVv1Z-00EgLK-M7 for pgsql-general@arkaria.postgresql.org; Tue, 15 Aug 2023 14:27:57 +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 1qVv1Y-00EgLB-Um for pgsql-general@lists.postgresql.org; Tue, 15 Aug 2023 14:27:57 +0000 Received: from mout-u-204.mailbox.org ([2001:67c:2050:101:465::204]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qVv1W-000IRZ-2A for pgsql-general@lists.postgresql.org; Tue, 15 Aug 2023 14:27:56 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4RQDBW0NNWz9scM; Tue, 15 Aug 2023 16:27:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1692109667; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yFQakfJMIqK+4dZiekXGuwNXo0V5xpXQ7o8AwkpV9Z8=; b=PCb4yl4mqZBXXHN9pK2mjxbHLjhcZqW9PcWO08tP/DldIUk9xtgV4le1BScqo02CkuL0q5 YkPysOUEvC9ySvYIe8EQ6dd9lJPUfab1HUU/nK/3eobU/X+wvU+zxcPi0ZEa04ZT/+kdWI Hq7r+VNoeheZYrqmLifA2xP07O88y65F4vdStd9v1lB+cpBIt4bzjRfoK5FuhO1W4QMKfA +PUnGfbfeXJMnlWknZAVQzQNZ/kWqTRMHz/2P7Edr+oxoe+xmozEmUlOepN0I9Zr6Fjgsx leUbKwydcDrYuUic2ebJCrxAGA9rAo0PMQIZxqkJ5YAomefs8yEoWPsJpLr5yg== Date: Tue, 15 Aug 2023 16:27:46 +0200 (CEST) From: Erik Wienhold To: "[Quipsy] Markus Karg" , "pgsql-general@lists.postgresql.org" Message-ID: <912969400.228946.1692109666429@office.mailbox.org> In-Reply-To: References: <533487381.212078.1692100096551@office.mailbox.org> Subject: Re: AW: Cast INTEGER to BIT confusion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 15/08/2023 13:59 CEST [Quipsy] Markus Karg wrote: > > Is setting the search path something that has to be done for each new > connection / each user, or is this something static and global for the > database? The search path is set per connection and the initial search path can be configured on the database and/or individual roles: 1. ALTER DATABASE mydb SET search_path = ... 2. ALTER ROLE myrole SET search_path = ... 3. ALTER ROLE myrole IN DATABASE mydb SET search_path = ... Those three statements do not affect your current connection though. Users can still set a different search path after connecting. -- Erik