Horton

Re: Core Extensions relocation

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-07-05T15:31:38Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Updates to contrib/isn ISBN tables.

  2. Add a "LIKE = typename" clause to CREATE TYPE for base types. This allows

On Sat, Jun 11, 2011 at 12:38 PM, Greg Smith <greg@2ndquadrant.com> wrote:
> Peter Eisentraut wrote:
>> For the directory name, I'd prefer either src/extensions (since there is
>> more than one), or if you want to go for short somehow, src/ext.  (Hmm,
>> I guess the installation subdirectory is also called "extension".  But
>> it felt wrong on first reading anyway.)
>
> I jumped between those two a couple of times myself, settling on "extension"
> to match the installation location as you figured out.  Assuming that name
> shouldn't change at this point, this seemed the best way to name the new
> directory, even though I agree it seems weird at first.
>
>> What version did you branch this off? :)
>
> Long enough ago that apparently I've missed some major changes; Magnus
> already pointed out I needed to revisit how MODULEDIR was used.  Looks like
> I need to rebuild the first patch in this series yet again, which shouldn't
> be too bad.  The second time I did that, I made the commits atomic enough
> that the inevitable third one would be easy.

Are you going to do this work for this CommitFest?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company