| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Inline Extension |
| Date: | 2012-01-19 17:12:02 |
| Message-ID: | E98FE4F0-DA5F-4719-BD1E-34DEE735B59B@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 19, 2012, at 7:21 AM, Dimitri Fontaine wrote:
> Now, for the dependency on a SQL file hosting the content, it's easier
> to just connect to the databases and get them the script in the SQL
> command rather than deploying a set of files: that means OS level
> packaging, either RPM or debian or some other variant. Or some other
> means of easily deploying the files. An SQL connection is all you need
> if you're not shipping .so.
ISTM that if you are managing 256 servers, you’re likely already using a packaging system for the deployment of application dependencies. In which case, to keep things consistent, you ought to distribute your extensions in exactly the same way.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-01-19 17:40:08 | Re: Group commit, revised |
| Previous Message | Simon Riggs | 2012-01-19 16:56:31 | Re: Publish checkpoint timing and sync files summary data to pg_stat_bgwriter |