| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | 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 12:28:02 |
| Message-ID: | 119d5cd5-4472-4ac7-1a96-6b30d0e42f0e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-04-09 12:30:39 | Re: pgsql: Store 2PC GID in commit/abort WAL recs for logical decoding |
| Previous Message | Amit Kapila | 2018-04-09 12:23:49 | Re: [sqlsmith] Failed assertion in create_gather_path |