| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation |
| Date: | 2020-04-08 06:06:39 |
| Message-ID: | 20200408060639.GG1606@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Apr 07, 2020 at 04:49:44PM +0900, Michael Paquier wrote:
> Thanks for the new version of the patch. I have been playing a bit
> today, and finished with the version attached. Some comments have
> been tweaked, and I have moved the test in the block with the other
> invalid cases for consistency, adding an extra test able to trigger a
> similar error within the transformation step where a parse context
> exists. It is a bit late now so I cannot push that today, but I'll
> do that tomorrow.
I was considering this stuff again, and I got cold feet regarding the
fact that we may be able to hit the case of a collation not set if the
type is collatable depending on how the restrictions now in place for
partition bound expressions get lifted in the future, so I have
committed what you sent as v1, after changing the first error message
to use "partition bound expression" and after adding a comment on top
of the new checks.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hugh Wang | 2020-04-08 06:51:14 | Re: BUG #16348: Memory leak when parsing config |
| Previous Message | Michael Paquier | 2020-04-08 02:23:45 | Re: [BUG] non archived WAL removed during production crash recovery |