| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | lakshmi <lakshmigcdac(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: create table like including storage parameter |
| Date: | 2026-10-06 07:52:34 |
| Message-ID: | CAHGQGwEBB=c-7psc6wB2bAvzJPQ3-Nrz1WR-LV4V0kYRdScr4A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 29, 2026 at 9:01 AM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
> On Tue, Apr 28, 2026 at 3:24 PM lakshmi <lakshmigcdac(at)gmail(dot)com> wrote:
> >
> > Hi all,
> >
> > I tested the patch on current HEAD.
> >
> > INCLUDING PARAMETERS works as expected. It correctly copies storage parameters. Duplicate parameters raise an error, and existing LIKE behavior remains unchanged.
So, if two source tables both set fillfactor, wouldn't
CREATE TABLE ... (LIKE t1 INCLUDING ALL, LIKE t2 INCLUDING ALL)
fail with this patch even though it succeeds today? I'm concerned that this
could be a backward compatibility issue.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2026-10-06 08:20:55 | Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes |
| Previous Message | Alexandre Felipe | 2026-10-06 07:44:53 | LWLock granular partition lock memory layout |