Re: pg_upgrade does not upgrade pg_stat_statements properly
От | Bruce Momjian |
---|---|
Тема | Re: pg_upgrade does not upgrade pg_stat_statements properly |
Дата | |
Msg-id | 20210729182855.GQ9600@momjian.us обсуждение исходный текст |
Ответ на | Re: pg_upgrade does not upgrade pg_stat_statements properly ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: pg_upgrade does not upgrade pg_stat_statements properly
Re: pg_upgrade does not upgrade pg_stat_statements properly |
Список | pgsql-hackers |
On Thu, Jul 29, 2021 at 10:00:12AM -0700, David G. Johnston wrote: > I'm warming up to "should" but maybe add a "why" such as "the old versions are > considered unsupported on the newer server". > > I dislike "usually via operating system commands", just offload this to the > extension, i.e., "must be installed in the new cluster via installation > procedures specific to, and documented by, each extension (for contrib it is > usually enough to ensure the -contrib package was chosen to be installed along > with the -server package for your operating system.)" > > I would simplify the first two sentences to just: > > If the old cluster used extensions those same extensions must be installed in > the new cluster via installation procedures specific to, and documented by, > each extension. For contrib extensions it is usually enough to install the > -contrib package via the same method you used to install the PostgreSQL server. > > I would consider my suggestion for "copy as-is/alter extension" wording in my > previous email in lieu of the existing third and fourth sentences, with the > "should" and "why" wording possibly worked in. But the existing works ok. I am sorry but none of your suggestions are exciting me --- they seem to get into too much detail for the context. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
В списке pgsql-hackers по дате отправления: