| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Thom Brown <thombrown(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Command Triggers, v16 |
| Date: | 2012-03-16 15:37:43 |
| Message-ID: | m2zkbg4kvs.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> there has to be some way to do that without breaking command triggers.
Sure, special case the switch branch in utility.c so as to return a
different command tag for ALTER TABLE and ALTER FOREIGN TABLE. For
precedents, see AlterObjectTypeCommandTag(ObjectType objtype) and
case T_DropStmt:
switch (((DropStmt *) parsetree)->removeType)
case T_DefineStmt:
switch (((DefineStmt *) parsetree)->kind)
So, do we want to do the same thing for ALTER FOREIGN TABLE, and should
I do that in the command triggers patch?
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-03-16 15:47:06 | Re: initdb and fsync |
| Previous Message | Robert Haas | 2012-03-16 15:27:57 | Re: Command Triggers, v16 |