Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: insert data with invalid input syntax for integer:"42P01"
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <2112371589.1866229.1549913142122@mail.yahoo.com>
Date: Mon, 11 Feb 2019 13:00:36 -0700
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
 Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <741DB90F-6C7A-4AEA-B2EB-DD37C5529AF4@elevated-dev.com>
References: <2112371589.1866229.1549913142122.ref@mail.yahoo.com>
 <2112371589.1866229.1549913142122@mail.yahoo.com>
To: Pepe TD Vo <pepevo@yahoo.com>
Precedence: bulk

> On Feb 11, 2019, at 12:25 PM, Pepe TD Vo <pepevo@yahoo.com> wrote:
>=20
> insert into cidrmgmt.errorlog(...)

For what it's worth, it seems likely the error is coming from that line =
(assuming you posted the correct procedure definition), thus that's the =
table whose definition matters. Further, the bad value is likely coming =
from the context, and there's no info here that would help figure out =
why there's "42P01" where an integer is required. But I can tell you =
that PG's nearest equivalent of Oracle's sys_context is untyped, always =
a string, so there would have to be a cast to an integer type. But of =
course you can't cast 42P01 to an integer, so that has to be figured out =
first.