From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] EnableDisableTrigger Cleanup & Questions |
Date: | 2008-11-06 14:01:57 |
Message-ID: | 17233.1225980117@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> While working on the join elimination patch, I was going through the
> trigger code and found quite a bit of nastiness in regard to naming
> and variable repurposing related to the addition of replication roles
> in 8.3. The most obvious issue is that tgenabled was switched from a
> bool to char to support replication roles. From a naming standpoint,
> the term "enabled" generally implies boolean and is fairly
> consistently used as such in other functions within the core. My
> initial preference would be to return tgenabled to its original
> boolean for use only in enabling/disabling triggers.
It would have been useful to make this criticism before 8.3 was
released. I don't think it's reasonable to change it now.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Benedek László | 2008-11-06 14:08:14 | Re: pg_dump roles support [Review] |
Previous Message | Simon Riggs | 2008-11-06 14:01:01 | Timing problem in DROP TABLESPACE? |