From: Tom Lane <tgl@sss.pgh.pa.us>
To: Erik Wienhold <ewie@ewie.name>
cc: SASIKUMAR Devaraj <sashikumard@yahoo.com>,
        pgsql-admin@lists.postgresql.org
Subject: Re: Sybase to postgres Timestamp column
In-reply-to: <fd4170a9-c849-4226-b6d0-35560b6a805b@ewie.name>
References: <1903154046.1708912.1769003607609.ref@mail.yahoo.com>
 <1903154046.1708912.1769003607609@mail.yahoo.com>
 <fd4170a9-c849-4226-b6d0-35560b6a805b@ewie.name>
Comments: In-reply-to Erik Wienhold <ewie@ewie.name>
	message dated "Wed, 21 Jan 2026 15:25:59 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2193942.1769007995.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Jan 2026 10:06:35 -0500
Message-ID: <2193943.1769007995@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2193943.1769007995%40sss.pgh.pa.us>
Precedence: bulk

Erik Wienhold <ewie@ewie.name> writes:
> 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

> I'm not familiar with Sybase.  What issues are you facing?
> But Postgres should accept this timestamp format without issue:

Yeah, I don't see a difficulty on the input side, so I'm guessing
the OP is wishing Postgres would output timestamps in that format.
Sorry, none of the built-in datestyle settings quite match that.
It's easy to replicate pretty closely using to_char():

postgres=3D# select to_char('Jan 21 2026 5:35 PM'::timestamp, 'Mon DD YYYY=
 HH:MI PM');
       to_char        =

----------------------
 Jan 21 2026 05:35 PM
(1 row)

But wrapping all your timestamp output columns in to_char() might be
more trouble than fixing the client-side code to accept ISO format.

			regards, tom lane