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 1swyst-00781C-Uq for pgsql-admin@arkaria.postgresql.org; Sat, 05 Oct 2024 07:07:24 +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 1swysr-00DJgV-2V for pgsql-admin@arkaria.postgresql.org; Sat, 05 Oct 2024 07:07:21 +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 1swysq-00DJgN-HN for pgsql-admin@lists.postgresql.org; Sat, 05 Oct 2024 07:07:20 +0000 Received: from mail-yb1-xb34.google.com ([2607:f8b0:4864:20::b34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1swysm-002dGx-Td for pgsql-admin@lists.postgresql.org; Sat, 05 Oct 2024 07:07:19 +0000 Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-e25d164854dso2504782276.2 for ; Sat, 05 Oct 2024 00:07:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lelarge-info.20230601.gappssmtp.com; s=20230601; t=1728112036; x=1728716836; 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=cfjKh51rlTzkVc6r7lqhrE6A0lbrhQiB+HQqVZbUp5I=; b=kcs4w1j5Z2Bj7WES3hmQRf9JdqaTJrx4rlBNXbSMKXQjXwvwOvLR1BGN6rr/ZMWmS2 zbG1M6oes7PGE+cC9hZJT2ZNyLcUlQlL6rrcTcUU8qHxbHfwivvr5SFQzjPpPxGG+oHw GAIoE5+VtIRUb0Vg/hGdTov3UsPyi3G1azIbTinkzBn7l9TN0NPN5lzV2h1jLOFCLO8u t9WZlkZhNscUS8cwNLsze4PwUdzkr2dNa0Pwtwz6JX8A/27U+Ow6C9TKpwXvqa+wBiwj 8k8LHEC5xJfPUTVwincAJQP5XU4+vjbtF7+HIStr0stkGzJ2JKLans7iDsBGdZib0qsj qkCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728112036; x=1728716836; 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=cfjKh51rlTzkVc6r7lqhrE6A0lbrhQiB+HQqVZbUp5I=; b=cHZXK2emdD3MfWGxRNlTkjk24+qkTYC2IZvEuFQANdATsL4NQWyTn4hVRT5JXM3ibE jVtCkrnCqEb5fbhaSp95dSahw+j1S3uDekOEiq2OJVdqEOanUlkVlYOS6/tu7w3+0hi/ 190JvqPSyoHyX9M6ovBd6VObTHoK7dyjrLs2IR3HxpC+LbqUQ3Y2ke6r0DXfxRbFjsfk fbMmN6HBPX1Q7nDxMI2LOqqK2IUtAdXbhuoHZNP7i0klhvPval+mOtr1NZvwcn+a91Cc 1ZMHMNdS0lL71DoXZR4e2L3v8zoxmcfZTDxpWNwXPZQ72Asa38m8L5nI5ePjztcK4QNS E73w== X-Forwarded-Encrypted: i=1; AJvYcCVjqDZBF41+2CulzdTK4sSHdfI9NnWL9ZSFrhyGYcNl0ZJeVe0QwQnye6W5nvEO3QlXs673WiEOIvAivg==@lists.postgresql.org X-Gm-Message-State: AOJu0YxjswZ1BoZKULL/biMzq2B5asXq2M7fiC8BYpUm2dbAmuIxgjbo F5Mlp4IaSeoMSiYSUdB0zLzK7mHC4ZbfulzajJmG8tT3F7v/xm6u7sP4z3HTj3NReBzQYQIGt58 SZCRBS75Hhf7u4Ef6qXHSrNdoQWJ+RrDQX0NFgw== X-Google-Smtp-Source: AGHT+IF6V3kMwrYN7hO6smMHxa/+kBPwEkKQN1s0S5WkjKxlpFLhtJgTVVXh7DPkhbFi5qm1ZRUIkSYdOHh3kSciO4U= X-Received: by 2002:a05:6902:1b07:b0:e1d:bce6:c97a with SMTP id 3f1490d57ef6-e28939628eemr3163399276.49.1728112036363; Sat, 05 Oct 2024 00:07:16 -0700 (PDT) MIME-Version: 1.0 References: <717426.1728080548@sss.pgh.pa.us> In-Reply-To: <717426.1728080548@sss.pgh.pa.us> From: Guillaume Lelarge Date: Sat, 5 Oct 2024 09:07:05 +0200 Message-ID: Subject: Re: Same Table Name - 2 Owners To: Tom Lane Cc: "David G. Johnston" , Sam Stearns , Pgsql-admin , Peter Garza , Henry Ashu Content-Type: multipart/alternative; boundary="0000000000000f619b0623b57005" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000f619b0623b57005 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, Le sam. 5 oct. 2024 =C3=A0 00:22, Tom Lane a =C3=A9crit= : > "David G. Johnston" writes: > > On Friday, October 4, 2024, Sam Stearns wrote: > >> Is it possible to do this in Postgres? > > > Within PostgreSQL, two objects can have the same name if they are of > > different types (note, relations is a fairly broad type category) or th= ey > > exist in different schemas. > > The Oracle case probably also works by putting the tables in different > schemas. I recall hearing that Oracle identifies "owner" with > "schema" much more closely than we do. > > +1 Great article on this topic: https://stormatics.tech/blogs/transitioning-from-oracle-to-postgresql-under= standing-the-concept-of-schema Regards. --=20 Guillaume. --0000000000000f619b0623b57005 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

Le=C2=A0sam. 5 oct. 2024 =C3=A0=C2=A000:22,= Tom Lane <tgl@sss.pgh.pa.us>= ; a =C3=A9crit=C2=A0:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Friday, October 4, 2024, Sam Stearns <sam.stearns@dat.com> wrote:
>> Is it possible to do this in Postgres?

> Within PostgreSQL, two objects can have the same name if they are of > different types (note, relations is a fairly broad type category) or t= hey
> exist in different schemas.

The Oracle case probably also works by putting the tables in different
schemas.=C2=A0 I recall hearing that Oracle identifies "owner" wi= th
"schema" much more closely than we do.


+1


Regards.


--
Guillaume.
--0000000000000f619b0623b57005--