Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1viZ9v-009vln-1E for pgsql-admin@arkaria.postgresql.org; Wed, 21 Jan 2026 14:26:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1viZ9u-007Sue-1n for pgsql-admin@arkaria.postgresql.org; Wed, 21 Jan 2026 14:26:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1viZ9u-007SuW-0W for pgsql-admin@lists.postgresql.org; Wed, 21 Jan 2026 14:26:10 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1viZ9q-001bcQ-1z for pgsql-admin@lists.postgresql.org; Wed, 21 Jan 2026 14:26:09 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4dx61k1sLFz9tXR; Wed, 21 Jan 2026 15:26:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1769005562; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wArS8UwErn0FVu8wjLOAbvk8BrmcfwD/NYNlG7jfoeY=; b=HbwsHJ7nqIyJb1mMBG9xslssF9dIQrihEJvo9MQWvz4mkDE7/7dHwEypPnUC5Hqt1Gdmgx RlDTg7AN513XPmEw7PdObH3GlNCsIp7EWn0AjH8w68AmzyBAkj2AvendsXqV+6nI9cOoIu MwgCxFdlMak6gQLilZAQe1nWl27DcyA1hq8bXWK6LWsOLFsUuqAlrBtWJsQk9EZYVlsyJ8 Mm5+WOXRuVH4JZUMumfj4YMVDr9S/oMmHk4yAwhiCIdiJHuz44Oa5NTKBLa++MqMAQgzxR 9Ic4nrzl26DZv6dH7JEi5go9SZRe1Pym0pPp/7cA3t/9yQaZ3QPJmKSr+4gshg== Date: Wed, 21 Jan 2026 15:25:59 +0100 From: Erik Wienhold To: SASIKUMAR Devaraj Cc: pgsql-admin@lists.postgresql.org Subject: Re: Sybase to postgres Timestamp column Message-ID: References: <1903154046.1708912.1769003607609.ref@mail.yahoo.com> <1903154046.1708912.1769003607609@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1903154046.1708912.1769003607609@mail.yahoo.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2026-01-21 14:53 +0100, SASIKUMAR Devaraj wrote: > When we are migrating from sybase to postgres, we are facing issues > with Timestamp field format and not matching. > Sybase format: Jan 21 2026 5:35 PM > Please advise any workaround is there? I'm not familiar with Sybase. What issues are you facing? Please provide more details such as database schema, error messages or expected vs. actual results. But Postgres should accept this timestamp format without issue: SELECT 'Jan 21 2026 5:35 PM'::timestamp; timestamp --------------------- 2026-01-21 17:35:00 (1 row) -- Erik Wienhold