| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Location for external scripts for Extensions? |
| Date: | 2013-10-25 12:20:25 |
| Message-ID: | 526A6209.3050804@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/24/13, 5:37 PM, Josh Berkus wrote:
> On 10/24/2013 02:36 PM, Peter Eisentraut wrote:
>> On 10/22/13, 2:27 PM, Josh Berkus wrote:
>>> 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.
>>
>> Use the SCRIPTS variable in pgxs, and they will get installed.
>>
>
> Oh yeah? Cool. Is there an existing extension with an example of this?
Don't know. I just saw this in the pgxs source code. Presumably, it
was added because it was used somewhere.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-10-25 12:29:45 | Re: Detection of nested function calls |
| Previous Message | Hugo Mercier | 2013-10-25 12:20:11 | Detection of nested function calls |