Re: Extension Packaging

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extension Packaging
Date: 2011-04-25 16:55:21
Message-ID: BANLkTi=VOuTLeF4r6UiHviV-G6tN6aWOig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 25, 2011 at 12:17 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> On Apr 25, 2011, at 9:14 AM, Aidan Van Dyk wrote:
>
>> Really, that means you just a sql function to your extension,
>> somethign similary to uname -a, or rpm -qi, which includes something
>> that is *forced* to change the postgresql catalog view of your
>> extension every time you ship a new version (major, or patch), and
>> then you get the exact version (and whatever else you include) for
>> free every time you update ;-)
>
> I think it's silly for every extension to have its own function that does this. Every one would have a different name and, perhaps, signature.

+1.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-04-25 16:59:49 Re: Unfriendly handling of pg_hba SSL options with SSL off
Previous Message Robert Haas 2011-04-25 16:54:02 Re: branching for 9.2devel