On Thu, Oct 6, 2016 at 12:44 PM, Amit Langote <langote_amit...@lab.ntt.co.jp > wrote:
> > Attached revised patches. Also, includes a fix for an issue reported by > Rajkumar Raghuwanshi [1] which turned out to be a bug in one of the later > patches. I will now move on to addressing the comments on patch 0003. > > Thanks a lot for the review! > > Thanks, > Amit > > [1] > https://www.postgresql.org/message-id/5dded2f1-c7f6-e7fc-56b > 5-23ab59495...@lab.ntt.co.jp Hi, 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" 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. !> Thanks & Regards, Rajkumar Raghuwanshi QMG, EnterpriseDB Corporation
