Message-ID: <77f369d02a34bdd1d1386227f1ec2d74d865aab4.camel@cybertec.at>
Subject: Re: Creating redwood datestyle in Postgres 12
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tim <timfosho@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Date: Thu, 25 Mar 2021 18:02:03 +0100
In-Reply-To: 
 <CAKhLO5i-PJdeX2q8eEzYVs91bzw1bDJxaSL_tD96XhnmGVAJfg@mail.gmail.com>
References: 
	<CAKhLO5jDy8bMop66WU8cNUFcfSuL1==FyGvawKZT-CC2FYuZXQ@mail.gmail.com>
	 <5273bd68ae53e76fb592249ba05433b4bb645660.camel@cybertec.at>
	 <CAKhLO5i-PJdeX2q8eEzYVs91bzw1bDJxaSL_tD96XhnmGVAJfg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/77f369d02a34bdd1d1386227f1ec2d74d865aab4.camel%40cybertec.at>
Precedence: bulk

On Thu, 2021-03-25 at 08:38 -0400, Tim wrote:
> Its a native ORACLE date formatting which shows like this: 08-JAN-99 04:05:06  set in the datestyle config param.
> 
> Currently running on EDB Advanced Server 12 which allows it as a datestyle configuration setting,
>  but looking to migrate off of there to native postgres pretty soon and was hoping there was some
>  way to have the same setting globally in native postgres. Which is starting to look like is not possible.

I concur.

You should use "to_char" in your queries or format timestamps in the client application.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com