| From: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, David Steele <david(at)pgmasters(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Mark Dilger <hornschnorter(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Boolean partitions syntax |
| Date: | 2018-04-09 13:41:31 |
| Message-ID: | 51B6F2FD-1443-40A8-B5DE-1C8B222A5F3C@excoventures.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Apr 9, 2018, at 8:28 AM, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 4/7/18 11:16, Jonathan S. Katz wrote:
>> The last line yielding:
>>
>> ERROR: syntax error at or near "TRUE"
>> LINE 3: FOR VALUES IN (TRUE);
>>
>> [Omitted from example: the “records_active” partition]
>>
>> I’m glad to see this was added to the open items. I would strongly
>> suggest fixing
>> this prior to the 11 release as it is unintuitive from a user standpoint
>> to use ‘TRUE’
>
> I think this is actually more accurately classified as an existing bug
> in PostgreSQL 10.
+1 based on running the above scenario on my 10.3 instance and
receiving the same error. Is there a chance the fix could make it into
10.4 then?
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-04-09 13:42:35 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Tomas Vondra | 2018-04-09 13:33:18 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |