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 1v3epU-001T00-Mo for pgsql-general@arkaria.postgresql.org; Tue, 30 Sep 2025 18:12:01 +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 1v3epS-00BXsY-Ec for pgsql-general@arkaria.postgresql.org; Tue, 30 Sep 2025 18:11:59 +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 1v3epR-00BXrV-BZ for pgsql-general@lists.postgresql.org; Tue, 30 Sep 2025 18:11:58 +0000 Received: from fhigh-b6-smtp.messagingengine.com ([202.12.124.157]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1v3epP-000k0v-0R for pgsql-general@postgresql.org; Tue, 30 Sep 2025 18:11:57 +0000 Received: from phl-compute-09.internal (phl-compute-09.internal [10.202.2.49]) by mailfhigh.stl.internal (Postfix) with ESMTP id C0E627A007D; Tue, 30 Sep 2025 14:11:54 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Tue, 30 Sep 2025 14:11:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= 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:subject:subject:to:to; s=fm1; t=1759255914; x=1759342314; bh=pjoxb55YwXOm3GnOmpLIexKbagNOJTadatYZmxkvycU=; b= KzghjHNisjAaZHVIghkMH4ExYG8hj/4t85brCGBAf0WVzXlIanfY5LvKHfFtUdNP nmy9iaCT98odQ+80UwhfNE07oxCF0P2zBG1j2MLLxWJ7fVU69DYmMeu6diGpX5Lw Q9wcXFGYSbPc3MZVDUeSN7+4UvVN6z6jf9zrplrgYyBjrDeIOlscdzy+/ITPtTft vfcHMZSCaFbhs6eDXL7mfVQ3jNklGSyQJcmJZUcyqUaHW3+TOCAaykv3aSXFhPS4 k+BOETLs3df1EO1/j0puDuJwYK3DYva5yeURv3SX+lr4BsMbCyD7VkVSfHnZLq6f 6fuhDJRNvkqXXgtcIPZOqw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1759255914; x=1759342314; bh=p joxb55YwXOm3GnOmpLIexKbagNOJTadatYZmxkvycU=; b=wijkQtOoMZN2Cs3oq vfMzZYuMMhGDCWM8bVKljXL1/A0RN1VdsWLw4LIN9uuaZsdIa9ok1EypsYt0cTKv OdSsRzJw0jh9f11Ds2H9J+1srNAB7gY3PeQ/g5fTzaZwpNF7Cu2SmCur196uG+fH CXsMQEzyUgl4MPLfw8+hLjpX55POV77k1QeCInBr+bFoqVf13YOT+vrHcDoElh8+ thgbKZkOeNpvB/3HKqsY/mPrGw8b8B1d+yqLwIbUsZGBU9bknnQNZGppstMsq3q5 VSLVt8kQ/hhBxfvdl8GnDujhARauAJEjsW2VI358cKR9c2IbR9GXg9Eya4JtVQfP 3lGDQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdekudegfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeetughrihgrnhcu mfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomheqne cuggftrfgrthhtvghrnheplefgteelteeifeelffevteffkedujefhleefuedujeetheeu vdffgffhjeelgfdtnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpphhoshhtghhrvg hsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspghrtg hpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepmhhruhguuhhlrgdr rghtthhilhhisehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrh grlhesphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 30 Sep 2025 14:11:53 -0400 (EDT) Message-ID: <01e5ec17-de91-4197-81d2-fa505802ab57@aklaver.com> Date: Tue, 30 Sep 2025 11:11:51 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Can't create a table with vector type as a non-super user To: mrudula attili , pgsql-general@postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 9/30/25 6:35 AM, mrudula attili wrote: > Hello Team, > > > Concern: > As its a production environment, we are not really happy to give away > the usage on public schema. > > Is there a way we could get the end users make use of the extension > without granting usage on public schema In addition to what Tom Lane suggested: https://github.com/pgvector/pgvector/blob/master/vector.control relocatable = true And per here: https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-RELOCATION " A fully relocatable extension can be moved into another schema at any time, even after it's been loaded into a database. This is done with the ALTER EXTENSION SET SCHEMA command, which automatically renames all the member objects into the new schema. Normally, this is only possible if the extension contains no internal assumptions about what schema any of its objects are in. Also, the extension's objects must all be in one schema to begin with (ignoring objects that do not belong to any schema, such as procedural languages). Mark a fully relocatable extension by setting relocatable = true in its control file. " You could move the extension to a schema that the users do have usage on. > > > Thanks, > SA > > > -- Adrian Klaver adrian.klaver@aklaver.com