Re: invalid memory alloc request size 18446744073709551614

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: clingareddy(at)vsoftcorp(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: invalid memory alloc request size 18446744073709551614
Date: 2016-02-03 15:47:40
Message-ID: 30967.1454514460@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

clingareddy(at)vsoftcorp(dot)com writes:
> While running a Query in PostgreSQL i am getting below error.

> SELECT count(1) ,SUM (DECODE(cr_ind, 'Y', NVL(numeric_amt, 0), 0)) cr_amt, SUM (DECODE(cr_ind, 'Y', 0, NVL(numeric_amt, 0))) db_amt , sum(decode(cr_ind, 'Y', 1, 0)) cr_cnt, sum(decode(cr_ind, 'Y', 0, 1)) db_cnt FROM ITEM_2015_1 a WHERE a.NUMERIC_AMT = 13066.00 and NVL(a.FLD_6_NUM,0) = 000014 and a.BUS_DATE = to_date('11212015','mmddyyyy') AND EXISTS (SELECT 1 FROM batch_master b WHERE a.BUS_DATE = b..BUS_DATE AND a.JOB_ID = b.JOB_ID AND a.BLK_NUM = b.BLK_NUM AND a.BCH_NUM = b.BCH_NUM )

> invalid memory alloc request size 18446744073709551614

Standard Postgres contains neither any nvl() function nor a four-argument
version of decode(). A theory worth considering therefore is that this
is a bug in whatever extension is providing those functions. If, as I
suspect, you're running EDB's version of Postgres, you would be well
advised to turn to them for support.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Keith 2016-02-03 16:28:11 Re: Re: Postgres 9.4 unlogged table. Under any circumstance after server crash would data persist?
Previous Message Gunnar "Nick" Bluth 2016-02-03 13:16:52 Re: invalid memory alloc request size 18446744073709551614