Bruce Momjian <[email protected]> writes:
> I assume the 'type' column will identify triggers, i/o functions
> (cstring), window functions, and maybe aggregates too; this solves
> several problems at once.
+1 for all except i/o functions. The cstring check for that was always
flat-out wrong, and getting it right is far more expensive than it's
worth --- AFAICS you'd have to grovel through all entries in pg_type.
But aggregates are only relevant if we decide to start showing
aggregates in \df --- is there consensus for that?
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
