Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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!
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2012-09-27 09:51:28|
|Subject: Re: autovacuum stress-testing our system|
|Previous:||From: Hannu Krosing||Date: 2012-09-27 08:44:06|
|Subject: Re: Switching timeline over streaming replication|