From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
Date: | 2024-05-25 17:53:17 |
Message-ID: | ZlIljQuKtXwn7I27@pryzbyj2023 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 03, 2024 at 04:32:25PM +0300, Alexander Korotkov wrote:
> On Fri, May 3, 2024 at 4:23 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> > Note that the error that led to "EXCLUDING IDENTITY" is being discused
> > over here:
> > https://www.postgresql.org/message-id/3b8a9dc1-bbc7-0ef5-6863-c432afac7d59@gmail.com
> >
> > It's possible that once that's addressed, the exclusion should be
> > removed here, too.
>
> +1
Can EXCLUDING IDENTITY be removed now ?
I wasn't able to find why it was needed - at one point, I think there
was a test case that threw an error, but now when I remove the EXCLUDE,
nothing goes wrong.
--
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2024-05-25 22:05:43 | Re: DROP OWNED BY fails to clean out pg_init_privs grants |
Previous Message | Xing Guo | 2024-05-25 15:52:22 | Fix an incorrect assertion condition in mdwritev(). |