From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Changes in Trigger Firing |
Date: | 2013-12-05 01:08:33 |
Message-ID: | CAB7nPqSu9EdQcFY6wLRyU-ag8pkC82z9T-Tf9WTwn=n36zJc=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-hackers |
On Wed, Dec 4, 2013 at 11:16 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Sameer Kumar wrote:
> I think you need better tools to guide you in exploring the source code.
> For example, you can use cscope to tell you where is CreateTrigStmt
> used, and you would find gram.y; and use it to tell you where
> CreateTrigger is used, and you would find utility.c.
>
> Any half-decent code editor should be able to generate a "database" of
> symbols and let you frolic around the various files quickly. Without
> that, anyone would be completely lost in developing new features of even
> the lowest complexity.
Not always, other people find as well git grep quite useful when
coding a complex tree. I read somewhere that "the best editor is the
one you master" (1) :)
1: http://www.postgresql.org/message-id/m2wrs6giyp.fsf@hi-media.com
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Dinesh Kumar | 2013-12-05 09:38:10 | Re: PATCH: Choose best width for Data Output columns of Query tool |
Previous Message | Sameer Kumar | 2013-12-04 17:56:38 | Re: Changes in Trigger Firing |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-12-05 01:17:47 | Re: Performance optimization of btree binary search |
Previous Message | Tom Lane | 2013-12-05 01:02:38 | Re: Status of FDW pushdowns |