Re: [DOCS] list of credits for release notes
Hello, 03.02.2018 00:56, Peter Eisentraut wrote: On 10/3/17 03:16, Alexander Lakhin wrote: While working on translation I've found a wrong name in credits: Fakhroutdinov Evgenievich That's how the name was entered in bug #14682. I understand it, and I found his real name by the email mentioned in the bug. So he just specified his name erroneously in the e-mail client. Should we preserve the error? (In fact I fixed the name in Russian translation because It looks ridiculous for Russians (as "Belmondo Paul(-son)" instead of "Jean-Paul Belmondo")). Best regards, Alexander
Update encryption options doc for SCRAM-SHA-256
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/encryption-options.html Description: Section "18.8. Encryption Options" only mentions MD5 as the password storage encryption mechanism, although PostgreSQL 10 introduced the superior SHA256 - somebody looking at the docs would get a bad idea of PostgreSQL's capabilities...
Re: [DOCS] list of credits for release notes
On 10/3/17 03:16, Alexander Lakhin wrote: > While working on translation I've found a wrong name in credits: > Fakhroutdinov Evgenievich That's how the name was entered in bug #14682. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Re: removal of md5 from example code
I think I get it, now. Is the reason for including the `pass` in the example so that the documentation can demonstrate `citext` along side case-sensitive text? If so, I struggle to come up with anything more obvious than a password hash for a case where case-sensitive comparison of text is necessary. The only other thing that comes to mind is an external system identifier like a Salesforce object id of a user. That would not be as universally obvious an example of case-sensitivity to all PostgreSQL users.. On Tue, Jan 30, 2018 at 10:02 PM, Peter Eisentraut < peter.eisentr...@2ndquadrant.com> wrote: > On 1/17/18 11:14, PG Doc comments form wrote: > > The documentation at > > https://www.postgresql.org/docs/current/static/citext.html shows an > example > > using md5 for password hashes. This is generally a bad practice and not > > relevant to the feature documented. > > > > I recommend removing the password column from this example or replacing > the > > md5 hash with something more secure (a secure hash algorithm with a > salt). > > We don't have any other hash functions built in and exposed at the SQL > level. (Maybe that is a problem.) Do you have any other ideas how to > rewrite that example? > > -- > Peter Eisentraut http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services >
estudent
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/tutorial-sql.html Description: Programação Java
