-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tom Lane wrote: > http://developer.postgresql.org/docs/postgres/catalog-pg-trigger.html > says "currently unused" and a desultory search through the sources > confirms that. I imagine it was put there with the intent of adding > column info later on. However, being a fixed-width array, I don't > actually see that it would be useful for anything much ... you'd at > least want to change it to a normal array. I grepped the sources and saw the same: I just wanted to make sure that nobody had any plans on it. If so, speak now, for I am planning on using it. As for the type, I presume you mean something like grolist in pg_group would be more applicable than indkey in pg_index. > BTW, if you don't have a convenient way of grepping the entire PG > source tree and quickly viewing all the hits on a particular symbol, > I *highly* recommend setting up something that can do that. I use > emacs + glimpse but there are probably newer tools out there. I actually use emacs and glimpse, but not together. I won't bother to ask if emacs has a glimpse-mode: it's emacs after all, so of course it does. :) I'll have to give it a shot. Thank, - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200503140712 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCNX/AvJuQZxSWSsgRAiq8AKD6+5GGa8Eh28acVHvx/0RZWpKBwwCgyDeD GojL9ZIFiUUDT0ZjIsuQ4Dk= =QivK -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
