Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.100.1.1.11\))
Subject: Re: Multiple schemas
From: Alban Hertroys <haramrae@gmail.com>
In-Reply-To: <12e2ffff149842d8762774e8ef307743cdb96736.camel@tpg.com.au>
Date: Thu, 24 Sep 2026 11:19:25 +0200
Cc: pgsql-general@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E874153D-C888-4941-9EF5-A151DFCE6E28@gmail.com>
References: <12e2ffff149842d8762774e8ef307743cdb96736.camel@tpg.com.au>
To: rob stone <floriparob@tpg.com.au>
Archived-At: 
 <https://www.postgresql.org/message-id/E874153D-C888-4941-9EF5-A151DFCE6E28%40gmail.com>
Precedence: bulk


> On 24 Sep 2026, at 10:24, rob stone <floriparob@tpg.com.au> wrote:
>=20
> Hello,
>=20
> I've been using a single schema in a database for years and I decided
> to try using multiple schemas in the same database.
>=20
> So, I set up a test database and followed the same procedure that I
> have used in the past but this time specifying multiple schemas.

=E2=80=A6

> show search_path;
>  search_path  =20
> ----------------
> "bsmdl, foots"
> (1 row)

I think there=E2=80=99s your problem. You have schemas named =E2=80=9Cbsmd=
l=E2=80=9D and =E2=80=9Cfoots=E2=80=9D, not a schema named "bsmdl, =
foots=E2=80=9D.

Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.