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 1v3clq-000zhR-9V for pgsql-general@arkaria.postgresql.org; Tue, 30 Sep 2025 16:00:06 +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 1v3clo-00Axrv-20 for pgsql-general@arkaria.postgresql.org; Tue, 30 Sep 2025 16:00:04 +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 1v3aVn-00A3kR-FR for pgsql-general@lists.postgresql.org; Tue, 30 Sep 2025 13:35:24 +0000 Received: from mail-ua1-x931.google.com ([2607:f8b0:4864:20::931]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v3aVh-000hsl-2N for pgsql-general@postgresql.org; Tue, 30 Sep 2025 13:35:23 +0000 Received: by mail-ua1-x931.google.com with SMTP id a1e0cc1a2514c-92cbfab6c0dso872346241.3 for ; Tue, 30 Sep 2025 06:35:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759239317; x=1759844117; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Af21AtCxopuAdZQzsu0q4V5zy3t56w8fDrLx/FkTfIA=; b=RmoZeVy5oXJptZwWoDGRq+Xz61SR3jWcUPjULrRBF5Xflm7BjDOk/vPMftALO9I/4R KJQO4OI1uAjGlwD4sTAWTRVsEXFm8PG5UBt6oHWitkueK8OH3pSxf6Rw1tgHP8c7DoED va6QyE1NpmNpavppW+zl6QJNJcbeXQUqICB0jtp7UHqcO5ppcNoIPDFllHl6BMYeL7b3 E2RjFIjwcYPKvEY9MRXhcRcyIGBJ7YnVrC0TBrfA0HOS3q6QEg/Fy5Pi0ONfcuHE5gbN 0JlExZDU7JOprrlIgUVtnlPmaz4uTSGah0vnGhgyvg7fExCIzFBNFZjZnQWVte9yMgUB AuWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759239317; x=1759844117; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Af21AtCxopuAdZQzsu0q4V5zy3t56w8fDrLx/FkTfIA=; b=cMMmLQ7qayO8Hq6zFO2B2jtJG76U3DsMGLGg4eL89zCV9pBYk7U0yi0Xg45lwFPdJA fdjEcfXcz+WD0FswZdR2ktWvAjBcEpGdLWssqf9/OWhb0I8/R797fPQwTgl7ce9wuatH sSlK9Th7pRXEa8+ZXGa/d0LRP21KaMYJSdDkUJQ1o8kLuXmROPqarkAHj++AVmKbFNkH H9NCLwNnsoeQMpG4G2MK/O4Vmuaqg99Fo5otF//iIRmXRo3qLoV0amVErQht0KdXrT1Y vdHK/E4pXI2anNLEyUlmnv6EtwMbfKxu9xAjsz3U3mgH1BEKMSa51zOMggEfOSMgX8p3 AiRw== X-Gm-Message-State: AOJu0YypWPycPFg0qE73NTeJs7J9gCvyM2qGnx8e2TeD6HzIdn9/SdZv s/YoNxW+RTl5Rz/obiGD8I1MeYNKwy283GWVvTl5B6vWRnmOoyMpU8wOLSYQD43XB3uwHz8hJFm QzHg600qflNmeYrHxvghSAoXS+CqYF0T/jSmw X-Gm-Gg: ASbGncs6t/5gQUEdvwdjR9CDwsrKQVMEOKOBj1wuO8J93gYzsM4DPYnt/7UdZxboovF eA5WwXYAyzZBjWoc250DDian1XdxjAFGy/gkirsxiGNmjbco1VYdrcCBiQzD/eXwT1Jgd9L+T29 PWXKcXIAY1rmf21Qe8Yy3amC6rQPbpbvAphFBl1w54q+8fxMozbd2RQ2eSFQqSg4t6oy27j/TDx xHtlT/VU3vkhTP5wxekXJFYOETIPzJ8 X-Google-Smtp-Source: AGHT+IHsCoa5RsWHNzlf9Oa6Ee74S2MRsppqlruxqCmW/E72XtBeHsjrPYGnlbXuuhf/oPLt3YeTORJNkhIywRVP5Ps= X-Received: by 2002:a05:6102:b03:b0:5a8:4256:1f14 with SMTP id ada2fe7eead31-5acd94bd965mr8252943137.35.1759239317502; Tue, 30 Sep 2025 06:35:17 -0700 (PDT) MIME-Version: 1.0 From: mrudula attili Date: Tue, 30 Sep 2025 14:35:06 +0100 X-Gm-Features: AS18NWD5ddbY350HAnUGFQMaUpkDAgkkRyilq_YV1tYCp4udXAn4nFmj4-IUVu8 Message-ID: Subject: Can't create a table with vector type as a non-super user To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000983d26064004d2b8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000983d26064004d2b8 Content-Type: text/plain; charset="UTF-8" Hello Team, I have recently installed the pgvector extension on one of our production databases. Managed to create the extension as super user and create table with the vector type. But a non super user (a read write user of the database) is not able to create a table with vector type and keeps getting the below error. CREATE TABLE items (id bigserial PRIMARY KEY, embedding vector(3)) [2025-09-30 09:22:29] [42704] ERROR: type "vector" does not exist [2025-09-30 09:22:29] Position: 57 Actions taken: 1. Granted usage of type vector to user - No luck 2. Granted usage on schema public to user - Worked 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 Thanks, SA --000000000000983d26064004d2b8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello Team,


I have recently installed the pgvector extension o= n one of our production databases.
Manag= ed to create the extension as super user and create table with the vector t= ype.

But a non super user (= a read write user of the database) is not able to create a table with vecto= r type and keeps getting the below error.

CREATE TABLE items (id bigserial PRIMARY KEY, embedding vect= or(3))
[2025-09-30 09:22:29] [42704] ERR= OR: type "vector" does not exist
[2025-09-30 09:22:29] Position: 57

Actions taken:

  1. Granted usage of type = vector to user
  • No luck
  1. Granted usage on schema public to user
=
  • Worked

Concern:
As its a production e= nvironment, we are not really happy to give away the usage on public schema= .

Is there a way we could g= et the end users make use of the extension without granting usage on public= schema

<= br>

Thank= s,
SA

<= br>


--000000000000983d26064004d2b8--