| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Brian Weaver <cmdrclueless(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: EVENT Keyword and CREATE TABLE |
| Date: | 2012-09-27 08:57:00 |
| Message-ID: | m2fw63yhb7.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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!
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-09-27 09:51:28 | Re: autovacuum stress-testing our system |
| Previous Message | Hannu Krosing | 2012-09-27 08:44:06 | Re: Switching timeline over streaming replication |