Tom Lane <t...@sss.pgh.pa.us> writes: > It's a bug. The event-trigger patch added EVENT as a new keyword, but > forgot to list it in the unreserved_keywords production, which is > necessary to make it actually act unreserved.
Oh. Oops. Sorry about that. > I've committed a fix, and manually verified there are no other such > errors at present, but this isn't the first time this has happened. > We probably need to put in some automated cross-check, or it won't > be the last time either. I see you've added the automated cross-check now, thanks for that! Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers