| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Venkata B Nagothi <nag1010(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Range Partitioning behaviour - query |
| Date: | 2017-02-24 01:17:23 |
| Message-ID: | 0aae38cf-5448-5eda-15f1-5ebd66b5ff8d@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/02/24 8:38, Venkata B Nagothi wrote:
> On Thu, Feb 23, 2017 at 3:14 PM, Amit Langote wrote:
>> Upper bound of a range partition is an exclusive bound. A note was added
>> recently to the CREATE TABLE page to make this clear.
>>
>> https://www.postgresql.org/docs/devel/static/sql-createtable.html
>
>
> Thanks. Actually, my confusion was that the upper bound value would be
> included when "TO" clause is used in the syntax.
Hmm, TO sounds like it implies inclusive.
> Also, there are no options like "<" or "LESS THAN" clauses available. So,
> "TO" translates to "<". That is what i wanted to confirm.
Yes, that's it.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-24 01:34:27 | Re: btree_gin and btree_gist for enums |
| Previous Message | Michael Paquier | 2017-02-24 00:29:54 | Re: Automatic cleanup of oldest WAL segments with pg_receivexlog |