Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W8rrz-0004v0-Pi for pgsql-sql@arkaria.postgresql.org; Thu, 30 Jan 2014 13:41:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W8rrz-0000e0-5B for pgsql-sql@arkaria.postgresql.org; Thu, 30 Jan 2014 13:41:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W8rry-0000dt-1O for pgsql-sql@postgresql.org; Thu, 30 Jan 2014 13:41:26 +0000 Received: from mail-am1lp0016.outbound.protection.outlook.com ([213.199.154.16] helo=emea01-am1-obe.outbound.protection.outlook.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W8rrs-0006Xx-5R for pgsql-sql@postgresql.org; Thu, 30 Jan 2014 13:41:25 +0000 Received: from AMSPR04MB211.eurprd04.prod.outlook.com (10.242.84.17) by AMSPR04MB209.eurprd04.prod.outlook.com (10.242.84.15) with Microsoft SMTP Server (TLS) id 15.0.868.8; Thu, 30 Jan 2014 13:41:16 +0000 Received: from AMSPR04MB211.eurprd04.prod.outlook.com ([169.254.1.232]) by AMSPR04MB211.eurprd04.prod.outlook.com ([169.254.1.232]) with mapi id 15.00.0868.013; Thu, 30 Jan 2014 13:41:16 +0000 From: Sandeep Devan To: "pgsql-sql@postgresql.org" Subject: "Timestamp out of range" Thread-Topic: "Timestamp out of range" Thread-Index: Ac8dv75j3Jp+eDbISkenVHaRY/AOVg== Date: Thu, 30 Jan 2014 13:41:15 +0000 Message-ID: <8c7644832d5a4861bd567bbabf2b2f29@AMSPR04MB211.eurprd04.prod.outlook.com> Accept-Language: en-IN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [61.95.179.194] x-forefront-prvs: 0107098B6C x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(199002)(189002)(164054003)(377424004)(76796001)(87936001)(76786001)(87266001)(85806002)(15975445006)(83072002)(74662001)(31966008)(74316001)(77096001)(69226001)(46102001)(76576001)(74502001)(93136001)(51856001)(85306002)(94946001)(74366001)(19580395003)(90146001)(2656002)(54316002)(92566001)(56816005)(83322001)(85852003)(81686001)(81816001)(81342001)(80976001)(94316002)(33646001)(81542001)(66066001)(15974865002)(56776001)(59766001)(77982001)(79102001)(47446002)(76176001)(53806001)(54356001)(76482001)(47976001)(65816001)(86362001)(63696002)(50986001)(93516002)(16601075003)(74706001)(4396001)(15202345003)(49866001)(80022001)(47736001)(74876001)(222603001)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR04MB209; H:AMSPR04MB211.eurprd04.prod.outlook.com; CLIP:61.95.179.194; FPR:AE0CD91D.8CF3DA48.B8DD6193.150CCC01.209F8; InfoNoRecordsA:0; MX:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_8c7644832d5a4861bd567bbabf2b2f29AMSPR04MB211eurprd04pro_" MIME-Version: 1.0 X-OriginatorOrg: in.rm.com X-Pg-Spam-Score: 0.4 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org --_000_8c7644832d5a4861bd567bbabf2b2f29AMSPR04MB211eurprd04pro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We have a .Net application which stores data in PostgreSQL. We have a perfe= ctly working code with PostgreSQL 8.3 and now we are trying to upgrade our = PostgreSQL server from version 8.3 to 9.3 and our code seems to break. For connecting PostgeSQL we are using 'OLEDB'. The issue we are getting is "Timestamp out of range". When looked through t= he logs receiving weird timestamp "152085-04-28 06:14:51.818821".