Updated the doc - PostgreSQL-part

[ackbyte]

Corrected the PostgreSQL statements, because of some typos.

[Thomas-Gelf]

Thanks for your contribution, @ackbyte! What went wrong with the original code block, didn't that work for you?

[ackbyte]

Hi @Thomas-Gelf, there are multiple issues, that getting fixed by this pull request:

1. faulty SQL-Statement syntax, which is not run able because of missing quotation marks
2. mixing multiple execution styles of the statements. One from inside the psql-shell and the other one from the bash-shell

BR
ackbyte

[Thomas-Gelf]

Did you try to paste the whole block at once?

[ackbyte]

@Thomas-Gelf, no. Because one part of the block is optional... as described in the documentation as an optional part.
So the whole block has also to be spitted to fit the description.

[Thomas-Gelf]

IMHO we should better no longer state that it is "optional" :D Thanks for pointing me to this. Of course if you leave out part of the statement you are required to do so in a correct way. And having separate statements would obviously make it easier to do so. But apart from that, the original block should be correct - isn't it? Or do I miss something?

[ackbyte]

That's correct @Thomas-Gelf ;) When pgcrypto gets mandatory part - the origin block is correct and can be used as it is :)

[Thomas-Gelf]

Thanks @ackbyte! I'll double-check this and then either merge your pull request or declare the "optional" part being required.

[cla-bot]

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @ackbyte

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.

• If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.