| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Andy <frum(at)ar-sd(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Problem Setting DateStyle |
| Date: | 2006-06-26 16:11:02 |
| Message-ID: | 1151338262.4215.51.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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;
> DateStyle
> SQL, DMY
>
> >>>>>>>>>> this should be the good result.
>
> Now the tries:
> Edit the postgresql.conf. Set datestyle = 'SQL, DMY' parameter. Restart the
> 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?
I'd try to alter the database to have a certain datestyle and see if
that helps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlos H. Reimer | 2006-06-26 17:39:40 | Hiding table structure information |
| Previous Message | Tom Lane | 2006-06-26 16:10:43 | Re: Aborting transactions |