It's allowed to specify an non-default opclass in partition by clause, but I do not see any testcase testing the same. Can you please add one.
On Fri, Oct 7, 2016 at 2:50 PM, Amit Langote <langote_amit...@lab.ntt.co.jp> wrote: > On 2016/10/07 17:33, Rajkumar Raghuwanshi wrote: >> On Thu, Oct 6, 2016 at 12:44 PM, Amit Langote wrote: >> I have applied latest patches, getting some error and crash, please check >> if you are also able to reproduce the same. >> >> Observation1 : Not able to create index on partition table. >> -------------- >> CREATE TABLE rp (c1 int, c2 int) PARTITION BY RANGE(c1); >> CREATE TABLE rp_p1 PARTITION OF rp FOR VALUES START (1) END (10); >> CREATE TABLE rp_p2 PARTITION OF rp FOR VALUES START (10) END (20); >> >> CREATE INDEX idx_rp_c1 on rp(c1); >> ERROR: cannot create index on partitioned table "rp" > > This one is a new behavior as I mentioned earlier in my previous email. > >> Observation2 : Getting cache lookup failed error for multiple column range >> partition >> -------------- >> CREATE TABLE rp1_m (c1 int, c2 int) PARTITION BY RANGE(c1, ((c1 + c2)/2)); >> >> CREATE TABLE rp1_m_p1 PARTITION OF rp1_m FOR VALUES START (1, 1) END (10, >> 10); >> ERROR: cache lookup failed for attribute 0 of relation 16429 >> >> Observation3 : Getting server crash with multiple column range partition >> -------------- >> CREATE TABLE rp2_m (c1 int, c2 int) PARTITION BY RANGE(((c2 + c1)/2), c2); >> CREATE TABLE rp2_m_p1 PARTITION OF rp2_m FOR VALUES START (1, 1) END (10, >> 10); >> server closed the connection unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. >> The connection to the server was lost. Attempting reset: Failed. >> !> > > Fixed. Should have been caught when running the regression tests after I > made changes to 0001 to address some review comments (apparently there was > no test in 0003 that would've caught this, so added a new one, thanks!). > > > Attached updated patches. > > Thanks, > Amit -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
