Re: Modifying and solidifying contrib

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Huxton <dev(at)archonet(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, David Fetter <david(at)fetter(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Modifying and solidifying contrib
Date: 2007-02-07 03:36:36
Message-ID: A9A9F043-5F1F-402C-A435-ED2D8F2945C4@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Feb 5, 2007, at 11:19 AM, Andrew Dunstan wrote:
> Jim Nasby wrote:
>> There was also mention of having a means to tell pg_dump not to
>> dump extensions...
> What's the use case for that? What will we do if there are db
> objects that depend on some extensions? Given that there will be
> some uninstall support, this one seems less necessary.

In addition to Martijn's tsearch case, there's also PostGIS. And I
believe this is a pretty big pain for them.

> I really think we should approach this by not trying to do
> everything at once.

That's fine; I just wanted to point out the use case while lists were
being made.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2007-02-07 03:43:48 Re: 10 weeks to feature freeze (Pending Work)
Previous Message Jim Nasby 2007-02-07 03:31:55 Re: Proposal: Commit timestamp