BUG #14667: Question on money type as the key of partitioned table

From: csjy_tsb(at)163(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14667: Question on money type as the key of partitioned table
Date: 2017-05-24 02:52:55
Message-ID: 20170524025255.29945.43057@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14667
Logged by: tian bing
Email address: csjy_tsb(at)163(dot)com
PostgreSQL version: 10beta1
Operating system: centos6.4
Description:

Hi,
When I use the money type as the key to create the partition table as
follows:

postgres=# create table test(m money) partition by list(m);
CREATE TABLE
postgres=# create table test_1 partition of test for values in (10);
CREATE TABLE

Partition bounds without apostrophe can be createed, but it store the null
value,not '10' value.

In fact, Correct grammar for creating partition is with apostrophe like
this:
postgres=# create table test_1 partition of test for values in ('10');

But the first creating partition without apostrophe should report an error
like "ERROR: operator does not exist: money = integer" as adding a check
constraint.

Looking forward to your reply.

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2017-05-24 03:25:17 Re: [HACKERS] Concurrent ALTER SEQUENCE RESTART Regression
Previous Message Robert Haas 2017-05-24 02:47:07 Re: [HACKERS] Concurrent ALTER SEQUENCE RESTART Regression