Nick Martens <[EMAIL PROTECTED]> writes:
> i just tried the commands from the psql console, and seems to crash then too.
It turns out that the problem is specific to referencing a timezone name
that is a directory (rather than an individual datafile) in the timezone
database. In that case the tzl
i just tried the commands from the psql console, and seems to crash then too.
mydb=# SET TimeZone TO 'America/Indiana';
ERROR: unrecognized time zone name: "America/Indiana"
mydb=# SELECT memo_id, memo_title, memo_comment,
mydb-# memo_date::timestamp, bedrijf_id, persoon_id, initialenachternaam,
Nick Martens <[EMAIL PROTECTED]> writes:
> here it is, including the defenition of the table and view in question, as it
> seems it coredumped when it tried to execute a query using a typecast from
> timestamptz to timestamp, after setting an invalid timezone, hope it helps.
Ah, that's the missin
here it is, including the defenition of the table and view in question, as it
seems it coredumped when it tried to execute a query using a typecast from
timestamptz to timestamp, after setting an invalid timezone, hope it helps.
Nick.
ps. there are some strangely named columns as the db is bein
Nick Martens <[EMAIL PROTECTED]> writes:
> Jan 10 17:14:40 dndwebdev01 postgres[17374]: [1-1] ERROR: unrecognized time
> zone name: "America/Indiana"
> Jan 10 17:14:40 dndwebdev01 kernel: pid 17374 (postgres), uid 70: exited on
> signal 11 (core dumped)
Doesn't happen for me:
regression=# set
Hello, I am developing an php application and by mistake a wrong timezone was
set after I initialized the connection, which resulted in a core dump of the
current process.
The postgres version is 8.0.3 running on a freebsd 6.0-RELEASE machine with
the generic kernel.
I tried searching for simila
