| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)toroid(dot)org> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: git cherry-pick timestamping issue |
| Date: | 2010-09-23 22:04:58 |
| Message-ID: | 5537.1285279498@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Abhijit Menon-Sen <ams(at)toroid(dot)org> writes:
> I'm using 1.7.3, yes. It has a bunch of timezone handling changes, but
> I'm not sure if there's anything related to your problem. If you don't
> have TZ set in your environment, I suppose the following patch *could*
> be relevant, since you're in -0400 and I'm in +0530. I haven't tried
> to verify this, but if cat-file -p on your backported commit shows an
> absurdly high timezone value, then that's the problem.
Well, I do keep TZ set, but anyway an update to 1.7.3 seems like a good
idea on general principles. Will try it.
[ experiments a bit ... ] Hm, my Fedora 13 machine isn't showing this
behavior, even though it's also 1.7.2.3 and I don't see any
possibly-related patches being carried by Fedora. Odd.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-09-23 22:11:43 | Re: Configuring synchronous replication |
| Previous Message | Alvaro Herrera | 2010-09-23 21:51:35 | Re: git cherry-pick timestamping issue |