Re: Portal->commandTag as an enum
От | Mark Dilger |
---|---|
Тема | Re: Portal->commandTag as an enum |
Дата | |
Msg-id | 3EBECD98-44BD-44B2-9035-3C59B59D6A2B@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Portal->commandTag as an enum (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: Portal->commandTag as an enum
|
Список | pgsql-hackers |
> On Mar 2, 2020, at 9:08 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > On 2020-Mar-02, Alvaro Herrera wrote: > >> Here's the patch I propose for commit. I also rewrote the commit >> message. > > BTW I wonder if we should really change the definition of > EventTriggerData. ISTM that it would be sensible to keep it the same > for now ... I think it is more natural to change event trigger code to reason natively about CommandTags rather than continuing to reasonabout strings. The conversion back-and-forth between the enum and the string representation serves no useful purposethat I can see. But I understand if you are just trying to have the patch change fewer parts of the code, and ifyou feel more comfortable about reverting that part of the patch, as the committer, I think that's your prerogative. Did you want to do that yourself, or have me do it and resubmit? — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: