Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kjpnN-0004SY-Hd for pgsql-bugs@arkaria.postgresql.org; Mon, 30 Nov 2020 20:29:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kjpnK-0008AQ-QA for pgsql-bugs@arkaria.postgresql.org; Mon, 30 Nov 2020 20:29:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kjpnK-0008AJ-K1 for pgsql-bugs@lists.postgresql.org; Mon, 30 Nov 2020 20:29:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kjpnF-0006Uq-QO for pgsql-bugs@lists.postgresql.org; Mon, 30 Nov 2020 20:29:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0AUKT3Oh1305259; Mon, 30 Nov 2020 15:29:03 -0500 From: Tom Lane To: anjithapaul@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16753: 'expected 2-element int8 array' error while getting data using query with subquery In-reply-to: <16753-0e156a5fd6cee2d3@postgresql.org> References: <16753-0e156a5fd6cee2d3@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 30 Nov 2020 18:17:59 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1305257.1606768143.1@sss.pgh.pa.us> Date: Mon, 30 Nov 2020 15:29:03 -0500 Message-ID: <1305258.1606768143@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > I am using timescale db on top of postgres db. > ... > When I am trying to get data from aggregated_data table using below query, I > am getting error 'expected 2-element int8 array' I'm guessing you need to complain to the timescale folks; I don't think there's any such error message in core Postgres. regards, tom lane