On Thu, Apr 14, 2011 at 11:16:03PM -0400, Tom Lane wrote: > David Fetter <da...@fetter.org> writes: > > On Thu, Apr 14, 2011 at 10:43:16AM -0400, Tom Lane wrote: > >> ... I think a lot of this ultimately traces to the extensible, > >> data-type-agnostic design philosophy. The fact that we don't > >> know what an integer is until we look in pg_type, and don't know > >> what an "=" operator does until we look up its properties, is > >> great from a flexibility point of view; but this sort of query is > >> where the costs become obvious. > > > Is it time to revisit that decision? > > Umm ... what are you proposing?
Having a short, default path for the "only built-ins" case. Presumably people who create their own data types, operators, etc., understand that there's a performance trade-off for the feature. Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
