TIME ZONE is set to unknow in the conf file. The server syncs with NTP, has the correct time, but there is no TMZ env variable set. I set the recovery.conf to an hour before I want it and the logs show the time I wanted during DST. For example if I want a PITR of 9:55 AM, I put in 8:55 AM on the recovery.conf file, then the logs show a restore time of 9:55 AM was requested, and that's what gets processed. The non-DST part of the year, PITR works as expected and no adjustment is necessary. > Date: Thu, 15 Jul 2010 14:34:11 -0500 > From: Kevin.Grittner@xxxxxxxxxxxx > To: bitsandbytes88@xxxxxxxxxxx; pgsql-admin@xxxxxxxxxxxxxx > Subject: Re: tablespaces > > dx k9 <bitsandbytes88@xxxxxxxxxxx> wrote: > > > Has anyone noticed that doing a PITR during DST (March-November) > > has the effect of being one ahead. Now I just adjust the > > requested time an hour earlier, but is there a better way? > > I haven't noticed any odd behavior with PITR around Daylight Saving > Time boundaries. Could you describe exactly how you have it set up > and what you're seeing? > > -Kevin The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy. |