From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Subject: | Re: Location for external scripts for Extensions? |
Date: | 2013-10-23 16:24:27 |
Message-ID: | 5267F83B.7030601@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dimitri,
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> pg_partman has several external (python) scripts which help the
>> extension, located in /extras/ in its source. The problem currently is
>> that if you install pg_partman via pgxn or package, you don't get those
>> scripts, because there's no "install" location for them.
>
> See also my proposal to solve that, I'd welcome some design level
> discussions about it:
>
> http://www.postgresql.org/message-id/m28uyzgof3.fsf@2ndQuadrant.fr
Well, that's a bit more complicated than what I had in mind. I was
thinking just a location like $PGSHARE/extensions/lib/
Note that, in the case of pg_partman, we're talking about external
scripts designed to be run by hand, not libaries to be called by the PL
functions.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Kumar | 2013-10-23 16:37:42 | Re: Using indexes for ORDER BY and PARTITION BY clause in windowing functions |
Previous Message | Stephen Frost | 2013-10-23 16:20:38 | Re: Add min and max execute statement time in pg_stat_statement |