Re: I suggest improving install steps for CentOS 8

[Daniel Gustafsson]

Adding -www as this isn't a documentation issue but a website issue.

> On 14 Nov 2019, at 03:36, Yasuhiro Horimoto  wrote:
> 
> Hello,
> 
> I have found a problem with the following page.
> 
> page: https://www.postgresql.org/download/linux/redhat/
> 
> I tried install PostgreSQL12 into CentOS 8 as written on this page.
> However, I couldn't install it by the following error.
> 
> 
> # dnf install -y 
> https://download.postgresql.org/pub/repos/yum/reporpms/EL-8-x86_64/pgdg-redhat-repo-latest.noarch.rpm
> # dnf install -y postgresql12
> Failed to set locale, defaulting to C
> PostgreSQL 10 for RHEL/CentOS 8 - x8 100 kB/s | 539 kB 00:05
> PostgreSQL 11 for RHEL/CentOS 8 - x8 121 kB/s | 629 kB 00:05
> PostgreSQL 12 for RHEL/CentOS 8 - x8  91 kB/s | 471 kB 00:05
> PostgreSQL 9.4 for RHEL/CentOS 8 - x  75 kB/s | 361 kB 00:04
> PostgreSQL 9.5 for RHEL/CentOS 8 - x 108 kB/s | 425 kB 00:03
> PostgreSQL 9.6 for RHEL/CentOS 8 - x  55 kB/s | 518 kB 00:09
> No match for argument: postgresql12
> Error: Unable to find a match
> 
> 
> There is a workaround for this problem.
> I executed a below command.
> I could install it.
> 
> # dnf module disable postgresql
> 
> This problem has already reported to Red Hat Bugzilla.
> (https://bugzilla.redhat.com/show_bug.cgi?id=1718201#c1)
> 
> However, this problem has been already closed.
> Because it seems that is not a bug.

Agreed, it's not a bug.

> Therefore I suggest that add a workaround in this document like an
> attachment.
> 
> Thanks,
> diff --git a/templates/pages/download/linux/redhat.html 
> b/templates/pages/download/linux/redhat.html
> index 568085a..3b0cbaf 100644
> --- a/templates/pages/download/linux/redhat.html
> +++ b/templates/pages/download/linux/redhat.html
> @@ -51,6 +51,9 @@ The PostgreSQL Yum Repository currently supports:
> *Note: due to the shorter support cycle
> on Fedora, all supported versions of PostgreSQL are not available on this 
> platform. We do not recommend
> using Fedora for server deployments.
> +
> +*Note: PostgreSQL can't install in CentOS 8 
> or RedHat Enterprise 8 just execute the following steps.
> +We need to execute "dnf module disable postgresql" before install the client 
> package.

This doesn't explain what the problem is, and why the above command works (or
what side effects it may have).  I don't think it's a bad idea to mention this
problem on the page but we should phrase it in such a way that it's clear what
the underlying problem is, and what the fix means.  Linking to offical RPM docs
can be a good way too?

cheers ./daniel

Regarding Foreign data wrapper Import Schema

[PG Doc comments form]

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/11/sql-importforeignschema.html
Description:

Need little more clarification about OPTIONS ( option 'value' [, ...] ) on
Import schema feature. Like while importing i need to rename table as fdw
new name.

Re: Regarding Foreign data wrapper Import Schema

[Michael Paquier]

On Thu, Nov 14, 2019 at 09:21:21AM +, PG Doc comments form wrote:
> Need little more clarification about OPTIONS ( option 'value' [, ...] ) on
> Import schema feature. Like while importing i need to rename table as fdw
> new name.

Which paragraph(s) in the documentation do you suggest to improve and
how do you think these should be improved?
--
Michael


signature.asc
Description: PGP signature

no mention of GRANT USAGE in postgres_fdw docs

[PG Doc comments form]

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/12/postgres-fdw.html
Description:

The documentation page for postgres_fdw
 gives a nice
step by step on what's needed to configure a FOREIGN SERVER.  However, one
crucial step is missed, and that is that you need to issue GRANT USAGE ON
FOREIGN SERVER before you can successfully run step 4, IMPORT FOREIGN
SCHEMA.
Fortunately, I was able to get help on this from some kind folks in
#postgresql on IRC, but the documentation should be updated to include this
step.

Thanks,
--Joe