| From: | Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | remove unnecessary flag has_null from PartitionBoundInfoData |
| Date: | 2017-05-17 10:53:50 |
| Message-ID: | CAOgcT0NZ_30-pjBpW2OgneV1ammArHkZDZ8B_KFC3q+_Xb2H9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
As discussed in default partition thread[1]
<https://www.postgresql.org/message-id/CAFjFpRcvD-jf6z6-5mjx4tm-8NSj8Wnh%2B6%3DL6OB9Qy2yKX0HCg%40mail.gmail.com>,
here is the patch to remove
has_null from PartitionBoundInfoData structure.
Basically flag has_null is not needed and null_index can be checked if the
current bound is having a null value or not.
For simplicity of future use, in attached patch I have introduced a macro
that
would return TRUE if the given bound has null.
PFA.
Regards,
Jeevan Ladhe
| Attachment | Content-Type | Size |
|---|---|---|
| remove_has_null_PartitionBoundInfoData_v1.patch | application/octet-stream | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-05-17 10:57:19 | Re: statement_timeout is not working as expected with postgres_fdw |
| Previous Message | Dilip Kumar | 2017-05-17 10:35:01 | Re: UPDATE of partition key |