From: | Maksim Milyutin <milyutinma(at)gmail(dot)com> |
---|---|
To: | jesper(dot)pedersen(at)redhat(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Partitions: \d vs \d+ |
Date: | 2017-09-28 13:41:33 |
Message-ID: | 55cc8eb2-d913-5815-1a74-95332261cf8a@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28.09.2017 16:29, Jesper Pedersen wrote:
> On 09/28/2017 09:19 AM, Maksim Milyutin wrote:
>>> E.g. "No partition constraint" vs. "Partition constraint:
>>> satisfies_hash_partition(...)".
>>
>> I also noticed ambiguity in printing "No partition constraint" in
>> non-verbose mode and "Partition constraint:..." in verbose one for
>> partition tables regardless of the type of partition.
>> Attached small patch removes any output about partition constraint in
>> non-verbose mode.
>>
>
> Yeah, that could be one way.
>
> It should likely be backported to REL_10_STABLE, so the question is if
> we are too late in the release cycle to change that output.
I want to prepare more complete patch for "Partition constraint" output.
For example, I encountered the primitive output with repetitive
conjuncts for subpartition whose parent is partitioned by the same key:
Partition constraint: (/(i IS NOT NULL)/ AND (i >= 30) AND (i < 40) AND
/(i IS NOT NULL)/ AND (i = ANY (ARRAY[30, 31])))
--
Regards,
Maksim Milyutin
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-09-28 14:47:53 | pgsql: Fix freezing of a dead HOT-updated tuple |
Previous Message | Jesper Pedersen | 2017-09-28 13:29:29 | Re: Partitions: \d vs \d+ |