Brian Weaver <cmdrclueless@gmail.com> writes:
> In some of our old tables going back several years we a column named
> 'event' as in:
> event character varying(1000)
> I was working off trunk and the database refuses to create this table
> any longer. Is this by design or is it a regression bug?
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.
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.
regards, tom lane