Re: Location for external scripts for Extensions?

Lists: pgsql-hackers
From: Josh Berkus <josh(at)agliodbs(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Location for external scripts for Extensions?
Date: 2013-10-22 18:27:47
Message-ID: 5266C3A3.2050109@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

All,

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.

Where should these go? PGSHARE/pg_partman/? Or somewhere else? I'm
looking to set a canonical location for extensions with external scripts.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Location for external scripts for Extensions?
Date: 2013-10-22 19:25:43
Message-ID: m2li1lkszs.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support


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-24 21:36:13
Message-ID: 526992CD.4000104@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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.


From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Location for external scripts for Extensions?
Date: 2013-10-24 21:37:33
Message-ID: 5269931D.5040906@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


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
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.