Re: Extensions, this time with a patch

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, "David E. Wheeler" <david@kineticode.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2010-10-22T21:09:15Z
Lists: pgsql-hackers
Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> Anyway, my point is that by default there's no directory scanning: the
> lookup is first directed towards ${extension-name}.control, of
> course. Only when this file does not exists or its name property is
> different from the extension name do we get to scan the directory, and
> we stop as soon as we find the .control file with the right name in it.

This seems (a) way overcomplicated, and (b) sorely in need of a
unique-index mechanism.

Please just use the filenames and have done.  This is lily-gilding
at its finest.  People who want to use non-ascii filenames are welcome
to do so, and deal with any ensuing fallout themselves.

			regards, tom lane