X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A65889FA490 for ; Tue, 27 Jun 2006 04:12:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 24479-03 for ; Tue, 27 Jun 2006 04:11:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ar-sd.net (mail.ar-sd.net [81.196.35.136]) by postgresql.org (Postfix) with ESMTP id DFFED9FA395 for ; Tue, 27 Jun 2006 04:11:52 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 26A192CB40; Tue, 27 Jun 2006 10:07:02 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (ar-sd.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26119-06; Tue, 27 Jun 2006 10:06:57 +0300 (EEST) Received: from forge (forge.mpsro.dom [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id 1DC532B0CC; Tue, 27 Jun 2006 10:06:57 +0300 (EEST) Message-ID: <008b01c699b8$fee9df90$0b00a8c0@mpsro.dom> From: "Andy" To: "Aaron Bono" , "Scott Marlowe" Cc: "Tom Lane" , References: <014601c69928$3dd35740$0b00a8c0@mpsro.dom> <29135.1151333441@sss.pgh.pa.us> <003801c69933$58bad960$0b00a8c0@mpsro.dom> <1151338262.4215.51.camel@state.g2switchworks.com> Subject: Re: [SOLVED] Problem Setting DateStyle Date: Tue, 27 Jun 2006 10:12:03 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01C699D2.22C0CB40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/252 X-Sequence-Number: 22214 This is a multi-part message in MIME format. ------=_NextPart_000_0088_01C699D2.22C0CB40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ups, sorry folks,=20 I use pgadmin3 for database access and it seems that it executes SET = DateStyle=3DISO; every time it connects.=20 Same with phppgadmin4. If i connect with psql then it works fine.=20 Anyway good to know.=20 Best regards, Andy. ----- Original Message -----=20 From: Aaron Bono=20 To: Scott Marlowe=20 Cc: Andy ; Tom Lane ; pgsql-admin@postgresql.org=20 Sent: Tuesday, June 27, 2006 3:20 AM Subject: Re: [ADMIN] Problem Setting DateStyle Also, and I know this sounds stupid, you may check to see if the = database really restarted. I recently got a new server and for some = reason when I use the restart script found in /etc/init.d/postgres it = doesn't actually restart the server (the shutdown fails) but when I go = to the control panel installed by my ISP it restarts wonderfully. I saw = what was happening when I looked at the date the postgres process = started.=20 -Aaron On 6/26/06, Scott Marlowe wrote: On Mon, 2006-06-26 at 10:15, Andy wrote: > Steps: > 1. > show datestyle > DateStyle > ISO, DMY > > > 2. > set datestyle to 'SQL, DMY'; > show datestyle;=20 > DateStyle > SQL, DMY > > >>>>>>>>>> this should be the good result. > > Now the tries: > Edit the postgresql.conf. Set datestyle =3D 'SQL, DMY' parameter. = Restart the=20 > DB server. > show datestyle > DateStyle > ISO, DMY > > ... there is no change. > > the other try: > alter database test2 set datestyle to 'SQL, DMY'; > SQL executed. > show datestyle > DateStyle > ISO, DMY > > > the same... Have you set a date style for this particular database (not the = cluster) with an alter database statement before?=20 I'd try to alter the database to have a certain datestyle and see if that helps. ------=_NextPart_000_0088_01C699D2.22C0CB40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ups, sorry folks,
 
I use pgadmin3 for database access and = it seems=20 that it executes SET DateStyle=3DISO; = every time it=20 connects.
Same with phppgadmin4. If i connect with psql then = it works fine.=20
 
Anyway good to know.
 
Best regards,
Andy.
 
----- Original Message -----
From:=20 Aaron=20 Bono
Cc: Andy ; Tom Lane ; pgsql-admin@postgresql.org=
Sent: Tuesday, June 27, 2006 = 3:20=20 AM
Subject: Re: [ADMIN] Problem = Setting=20 DateStyle

Also, and I know this sounds stupid, you may check to = see if=20 the database really restarted.  I recently got a new server and = for some=20 reason when I use the restart script found in /etc/init.d/postgres it = doesn't=20 actually restart the server (the shutdown fails) but when I go to the = control=20 panel installed by my ISP it restarts wonderfully.  I saw what = was=20 happening when I looked at the date the postgres process started.=20

-Aaron

On 6/26/06, Scott=20 Marlowe <smarlowe@g2switchworks.com= >=20 wrote:
On=20 Mon, 2006-06-26 at 10:15, Andy wrote:
> Steps:
> = 1.
> show=20 datestyle
>      =20 DateStyle
>       ISO,=20 DMY
>
>
> 2.
> set datestyle to 'SQL, = DMY';
>=20 show datestyle;
>      =20 DateStyle
>       SQL,=20 DMY
>
> >>>>>>>>>> this = should be=20 the good result.
>
> Now the tries:
> Edit the=20 postgresql.conf. Set datestyle =3D 'SQL, DMY' parameter. Restart the =
>=20 DB server.
> show=20 datestyle
>      =20 DateStyle
>       ISO,=20 DMY
>
> ... there is no change.
>
> the = other=20 try:
> alter database test2 set datestyle to 'SQL, = DMY';
> SQL=20 executed.
> show = datestyle
>      =20 DateStyle
>       ISO,=20 DMY
>
>
> the same...


Have you set a = date style=20 for this particular database (not the cluster)
with an alter = database=20 statement before?

I'd try to alter the database to have a = certain=20 datestyle and see if
that=20 helps.

------=_NextPart_000_0088_01C699D2.22C0CB40--