On 18/08/06, Tom Lane [EMAIL PROTECTED] wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
No, it's a work of a simplistic perlscript IIRC. It simply looked for
the first match it could find, based on the list found in the registry
(the whole concept is a bit of an ugly hack, but it's the best
Oh, you didn't say you were on Windows
I did, but it was buried in the first paragraph...
Magnus, did you have a specific reason for choosing Europe/Dublin,
or was it just alphabetically first? Europe/London looks at least
marginally closer to what one would think GMT means:
Does it have
On 26/07/06, Tom Lane [EMAIL PROTECTED] wrote:
Alistair Bayley [EMAIL PROTECTED] writes:
The first line of output puzzles me: why is '1916-10-01 02:25:20'
2627158159 seconds before 2000-01-01, while '1916-10-01 02:25:21' is
2627156080 before; a difference of 2080 seconds, or 34m:40s.
What
On 28/07/06, Tom Lane [EMAIL PROTECTED] wrote:
Alistair Bayley [EMAIL PROTECTED] writes:
I was puzzled as to why it is set to Dublin when my machine's Time
Zone is GMT. I saw in the docs that in the absense of an entry in the
.conf file or a TZ environment variable results in a guess
(forwarded from pgsql-interfaces because no response there; can
anybody tell me if I really have a bug, or am just a bit dim?)
Hello,
Below is a test C program, which fetches some timestamp literals and
prints their internal representation, which is the number of seconds
after 2000-01-01,
