From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, 691525127(at)qq(dot)com |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14915: Create sub-partitioning using GENERATED ALWAYS AS IDENTITY will lead to system collapse. |
Date: | 2017-11-17 02:41:13 |
Message-ID: | 20eccceb-b321-3f91-3b29-b300fcb85474@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2017/11/17 11:05, Michael Paquier wrote:
> On Fri, Nov 17, 2017 at 10:52 AM, <691525127(at)qq(dot)com> wrote:
>> However, the server connection failed in actual implementation.
>> What is the reason for that? Will it be a bug?
>
> This issue is already discussed here, happening as well for typed
> tables (original bug is about typed tables, I bumped into the
> partition bit after more testing):
> https://www.postgresql.org/message-id/20171023074458.1473.25799@wrigleys.postgresql.org
> There is a patch which actually blocks any hole with an error message
> instead of actual support as this feature support requires a bit of
> refactoring when working on constraint clauses at parsing. And that's
> a work about which we are not completely sure what's the best
> direction to take, so for v10 things will likely go through the road
> of a feature-not-supported error.
Yeah, I think it would be nice to apply that patch so that 10.2 will give
an error for this usage.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | xyh | 2017-11-17 02:57:34 | BUG #14916: psql \r is invalid in PostgreSQL 10 |
Previous Message | Amit Kapila | 2017-11-17 02:28:13 | Re: 10.1: hash index size exploding on vacuum full analyze |