Feedback-ID: i76984098:Fastmail
Message-ID: <5466153d-3bc3-4553-a5b2-d4c5050fb1d5@aklaver.com>
Date: Fri, 1 Nov 2024 16:53:46 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Plans for partitioning of inheriting tables
To: thiemo@gelassene-pferde.biz,
 PostgreSQL General <pgsql-general@lists.postgresql.org>
References: <ea963edb-5437-4de6-bd2c-97c141a391b8@gelassene-pferde.biz>
 <5757acdc-39ed-4642-a449-26e47b1bcf95@gelassene-pferde.biz>
 <d9d6a2f4-379b-45f3-9005-ab047625c1a4@aklaver.com>
 <20241101094106.Horde.TwPSs9YUgJ5v-_M-4ltwoeh@webmail.gelassene-pferde.biz>
 <14c1eb8c-a853-43b3-a1ea-b105bfd6c99b@aklaver.com>
 <20241101182110.Horde.P_w6KptTjJNeM1X9Asg5bE3@webmail.gelassene-pferde.biz>
 <6bc57377-52e1-496a-b9d6-4cd9dc84d92e@aklaver.com>
 <CAKkG4_nV-+6rz-01pA-S5vD7ai2h_ujF1cDFoOBG10CCHgRfmg@mail.gmail.com>
 <20241101201600.Horde.Br4fPP8BFAAwzFoMaM8_eJS@webmail.gelassene-pferde.biz>
 <666c82fe-be27-4f32-99ad-8952a56f2282@aklaver.com>
 <8791c3bf-6fff-4db4-a29e-2679d2de0960@gelassene-pferde.biz>
 <ce5f42dd-9513-479a-b64f-2d05b0d22135@aklaver.com>
 <20241102001013.Horde.g70bTplHNWnh_M3vk9I-edj@webmail.gelassene-pferde.biz>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <20241102001013.Horde.g70bTplHNWnh_M3vk9I-edj@webmail.gelassene-pferde.biz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/5466153d-3bc3-4553-a5b2-d4c5050fb1d5%40aklaver.com>
Precedence: bulk

On 11/1/24 16:10, thiemo@gelassene-pferde.biz wrote:
> 
> Adrian Klaver <adrian.klaver@aklaver.com> escribió:
> 
>> On 11/1/24 13:47, Thiemo Kellner wrote:
>>> It looks to me basically to be a "create table A as select * from B 
>>> where false".
>>
>> No it more capable then that.
> 
> Yes, I wrote basically, not exactly.
> 
>> CREATE TABLE <some_tbl> LIKE <some_other_tbl> has  like_option which 
>> allows to transfer over more attributes of the table, for example 
>> defaults, constraints, indexes, etc.
> 
> But, to my understanding, no primary nor unique nor foreign constraint.
> 


"INCLUDING INDEXES

     Indexes, PRIMARY KEY, UNIQUE, and EXCLUDE constraints on the 
original table will be created on the new table. Names for the new 
indexes and constraints are chosen according to the default rules, 
regardless of how the originals were named. (This behavior avoids 
possible duplicate-name failures for the new indexes.)
"

FK's are not in the the INCLUDINGs, nor triggers.


-- 
Adrian Klaver
adrian.klaver@aklaver.com