From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_upgrade docs |
Date: | 2010-05-25 03:23:41 |
Message-ID: | AANLkTik3ea7hVQBi6A5bWUm3kjHuihpNHFVdN6XXPhgJ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 24, 2010 at 5:50 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> What is your point?
My point is that I think Stefan has a good point when he says this:
>> >> >> hmm that seems better thanks, however I just noticed that we don't have
>> >> >> a "general limitations" section. The way the docs are now done suggests
>> >> >> that there are not limitations at all (except for the two warnings in
>> >> >> the migration guide). Is pg_upgrade really up to the point where it can
>> >> >> fully replace pg_dump & pg_restore independent of the loaded (contrib)
>> >> >> or even third party modules(like postgis or custom datatypes etc)?
I think he is quite right to be concerned about these issues and if
the limitations in this area are not well-documented so that users can
easily be aware of them, then IMHO that is something we should
correct.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2010-05-25 03:25:18 | Re: (9.1) btree_gist support for searching on "not equals" |
Previous Message | Robert Haas | 2010-05-25 03:19:06 | Re: ExecutorCheckPerms() hook |