-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/07 15:23, Vivek Khera wrote:
>
> On Mar 12, 2007, at 6:08 PM, Martijn van Oosterhout wrote:
>
>> On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
>>> Would I be correct in understanding that every pre-8.0 cluster
>>> must be restarted
On Mar 12, 2007, at 6:08 PM, Martijn van Oosterhout wrote:
On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
Would I be correct in understanding that every pre-8.0 cluster
must be restarted in order for the OS changes to take affect?!?
Possibly, I imagine many C libraries would cache th
Martijn van Oosterhout writes:
> On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
>> Would I be correct in understanding that every pre-8.0 cluster
>> must be restarted in order for the OS changes to take affect?!?
> Possibly, I imagine many C libraries would cache the timezone data over
>
On Monday March 12 2007 4:08 pm, Martijn van Oosterhout wrote:
> On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
> > Would I be correct in understanding that every pre-8.0
> > cluster must be restarted in order for the OS changes to
> > take affect?!?
>
> Possibly, I imagine many C libraries
On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
> Would I be correct in understanding that every pre-8.0 cluster
> must be restarted in order for the OS changes to take affect?!?
Possibly, I imagine many C libraries would cache the timezone data over
a fork and might not motice the changes
On Monday March 12 2007 1:07 pm, Ed L. wrote:
> Does this mean that we need to restart these clusters in order
> to get the timezone updates from the OS? Are they cached in
> the postmaster?
Nevermind. I just found it via googling.
Would I be correct in understanding that every pre-8.0 cluster
We have a 7.4.6 cluster which has been running on an HP B.11.00
box for quite sometime. The IT group applied daylight savings
patches to the OS, but the cluster is still showing the
incorrect timezone:
$ psql -c "select now()"
now
---
2
Joseph Shraibman writes:
> Robert Treat wrote:
>
>> If you are running pre-8.0 versions you need to update your operating system
>> (as you indicated). If you running an any 8.x version, you need to be on
>> the most current corresponding 8.x.y release.
>>
> So what happens if you have an old os
> >> So what happens if you have an old os with a new postgresql install?
> >> Will CURRENT_TIMESTAMP always return the correct value even if the
> >> system 'date' command is showing the wrong time?
>
> > Yes.
>
> Unless the user changes the system's clock setting (ie, its notion of
> the curr
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Joseph Shraibman wrote:
>> So what happens if you have an old os with a new postgresql install?
>> Will CURRENT_TIMESTAMP always return the correct value even if the
>> system 'date' command is showing the wrong time?
> Yes.
Unless the user changes th
Joseph Shraibman wrote:
> Robert Treat wrote:
>
> > If you are running pre-8.0 versions you need to update your operating
> > system
> > (as you indicated). If you running an any 8.x version, you need to be on
> > the
> > most current corresponding 8.x.y release.
> >
> So what happens if you
Robert Treat wrote:
If you are running pre-8.0 versions you need to update your operating system
(as you indicated). If you running an any 8.x version, you need to be on the
most current corresponding 8.x.y release.
So what happens if you have an old os with a new postgresql install?
Will C
> I was trying to avoid getting into the gory details of which releases
> had which timezone fixes, but it seems I can't avoid it. The new FAQ
> item has the details:
>
> USA daylight saving time changes are included in PostgreSQL release
> 8.0.[4+], and all later major releases, e.g. 8.1
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > USA daylight saving time changes are included in PostgreSQL
> > release 8.0.[4+], and all later major releases, e.g. 8.1. Canada and
> > Western Australia changes are included in 8.0.[10+], 8.1.[6+], and
> > all later major releases. PostgreS
Bruce Momjian wrote:
> USA daylight saving time changes are included in PostgreSQL
> release 8.0.[4+], and all later major releases, e.g. 8.1. Canada and
> Western Australia changes are included in 8.0.[10+], 8.1.[6+], and
> all later major releases. PostgreSQL releases prior to 8.0 use the
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Steve Crawford wrote:
>> 1. What, exactly, was the point of moving away from the system zoneinfo
>> files and requiring PG admins to maintain yet another apparently
>> identical set of files?
The fact that not all systems use the zic database. We were t
Steve Crawford wrote:
> > I was trying to avoid getting into the gory details of which releases
> > had which timezone fixes, but it seems I can't avoid it. The new FAQ
> > item has the details:
> >
> > USA daylight saving time changes are included in PostgreSQL release
> > 8.0.[4+], and
Ed L. wrote:
>
> >From the FAQ:
>
>
> 1.14) Will PostgreSQL handle recent daylight saving time changes
> in various countries?
>
> PostgreSQL versions prior to 8.0 use the operating system's
> timezone database for daylight saving information. All current
> versions of Po
On Tuesday 06 February 2007 13:16, Ed L. wrote:
> From the FAQ:
>
>
> 1.14) Will PostgreSQL handle recent daylight saving time changes
> in various countries?
>
> PostgreSQL versions prior to 8.0 use the operating system's
> timezone database for daylight saving information. Al
From the FAQ:
1.14) Will PostgreSQL handle recent daylight saving time changes
in various countries?
PostgreSQL versions prior to 8.0 use the operating system's
timezone database for daylight saving information. All current
versions of PostgreSQL 8.0 and later contain up-
20 matches
Mail list logo
