Le jeudi 19 décembre 2013 14:01:17, Robert Haas a écrit :
> On Wed, Dec 18, 2013 at 10:05 AM, Alvaro Herrera
>
> wrote:
> > Stephen Frost escribió:
> >> * Dimitri Fontaine (dimi...@2ndquadrant.fr) wrote:
> >> > Basically with building `UNIT` we realise with hindsight that we
> >> > failed to buil
On Wed, Dec 18, 2013 at 10:05 AM, Alvaro Herrera
wrote:
> Stephen Frost escribió:
>> * Dimitri Fontaine (dimi...@2ndquadrant.fr) wrote:
>
>> > Basically with building `UNIT` we realise with hindsight that we failed to
>> > build a proper `EXTENSION` system, and we send that message to our users.
>
Stephen Frost escribió:
> * Dimitri Fontaine (dimi...@2ndquadrant.fr) wrote:
> > Basically with building `UNIT` we realise with hindsight that we failed to
> > build a proper `EXTENSION` system, and we send that message to our users.
>
> Little difficult to draw conclusions about what out 'hindsi
* Dimitri Fontaine (dimi...@2ndquadrant.fr) wrote:
> Here's my attempt:
>
> # Inline Extension, Extension Templates
>
> The problem with *Inline Extension* is the dump and restore policy. The
> contents of an extensions are not be found in a `pg_dump` script, ever.
You keep coming back to this a
Simon Riggs writes:
> On 17 December 2013 23:42, Tom Lane wrote:
>>> We aim to have the simplest implementation that meets the stated need
>>> and reasonable extrapolations of that. Text in a catalog table is the
>>> simplest implementation. That is not a reason to reject it, especially
>>> when
