Tom Lane <tgl@sss.pgh.pa.us> writes:
> Author: Tom Lane <tgl@sss.pgh.pa.us>
> Branch: master Release: REL8_1 [872c1497f] 2005-05-24 18:02:31 +0000
> Branch: REL8_0_STABLE Release: REL8_0_4 [a94ace079] 2005-05-24 18:02:55 +0000
> Branch: REL7_4_STABLE Release: REL7_4_9 [0a7b3a364] 2005-05-24 18:03:24 +0000
>
> Previous fix for "x FULL JOIN y ON true" failed to handle the case
> where there was also a WHERE-clause restriction that applied to the
> join. The check on restrictlist == NIL is really unnecessary anyway,
> because select_mergejoin_clauses already checked for and complained
> about any unmergejoinable join clauses. So just take it out.
It's easy enough to find it on the website too, or to search for some
other patch as I did this morning:
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=872c1497f
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=40608e7f949fb7e4025c0ddd5be01939adc79eec
Having your proposed output in there would be awesome, because the use
case of determining which releases contain the patch is a *huge* one of
course --- and gitweb searches are easy, fast and convenient.
Now I can't comment on the git_changelog tool chapter, so that's a
little Off Topic, but still. Can we do something about the gitweb
interface to include such a feature?
Regards,
--
dim
