Re: Extensions, this time with a patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extensions, this time with a patch
Date: 2010-10-22 21:09:15
Message-ID: 29135.1287781755@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-10-22 21:10:42 Re: Integer input functions for date and timestamp
Previous Message Robert Haas 2010-10-22 20:28:00 Re: Integer input functions for date and timestamp