From: | "Keith Woodell" <efesar(at)unm(dot)edu> |
---|---|
To: | <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | triggers in latest snapshot |
Date: | 2004-07-28 18:07:26 |
Message-ID: | DAEPLOBLGHIGDDNJMMOKCELCCJAA.efesar@unm.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
I may have discovered a bug in the latest Win32 snapshots. I wanted to let
you all know just in case this is not already being covered. If you need
information like crash dumps, database schema, etc etc etc, let me know.
I cannot run any trigger functions (pgplsql) that involve SELECT, INSERT,
UPDATE or DELETE. The postgres backend that's handling the request crashes
hard, though the main postmaster continues to run and handle requests. It
happens regardless of the frontend (PGAdmin III, PHP) and it's consistent
and reproducible.
A simple trigger function like this crashes it:
BEGIN
SELECT NULL;
END;
One other note, triggers run fine on the 7.4 production running on FreeBSD,
with the same data and database schema.
-Keith Woodell
System Administrator
Natural Heritage New Mexico
505-277-3822 ext 232, 505-277-3844 (fax)
Please report NHNM technical support issues at http://admin.heritage.unm.edu
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2004-07-28 19:10:35 | problems running initdb |
Previous Message | Andrew Dunstan | 2004-07-28 17:34:58 | Re: [HACKERS] Cannot initdb in cvs tip |