The Core Team requested this on the advice of legal counsel, because of the ongoing legal action to invalidate PostgreSQL related trademarks registered by Fundación PostgreSQL which conflict with those held by the project (through the PostgreSQL Community Association, or PGCA).Īnyone who has owned a trademark is aware that it is essential to defend them, otherwise you risk losing them. On 24th July 2023, Álvaro Hernández posted a blog on the Fundación PostgreSQL website regarding the PostgreSQL Core Team's request that the website moderation team reject any submitted content linking to Fundación PostgreSQL or their events. You will also need to look at the application for code that does comparisons of user-entered information taking advantage of MS SQL Server's typical case insensitivity.The PostgreSQL Community Association (PGCA) is issuing a news announcement to clarify recent comments around an ongoing trademark dispute. This conversion might be a good time to force data used in joins and comparisons to all upper or lower case. You will have to force data to upper or lower on both sides of text comparisons if case is not important to the operation and there is a chance of it being different. It is worth noting that for data comparisons, PostgreSQL is case sensitive and there is no option to change this behaviour. Remember, PostgreSQL is normally case sensitive! See With this issue in mind, I've decided to always ensure that my PostgreSQL user While I explicitlyĮntered the user name jenkins_TEST_SU, PostgreSQLĬreated the user as jenkins_test_su in all lowercase characters.Ĭhanging the command to connect to the following string worked without issue.įor quite some time with no resolution. The problem was how PostgreSQL created the user above. I was initially suspicious of my Docker configuration and how I was loading the pg_hba.confįile referenced in the error above, but that wasn't the issue. Psql: FATAL: password authentication failed for user "jenkins_TEST_SU"įATAL: no pg_hba.conf entry for host "192.168.0.100", user "jenkins_TEST_SU", database "postgres", SSL off I then tried to log in using the new Super User account I created aboveĪnd received an unexpected error. $ psql -U admin_user -h 127.0.0.1 -p 5432 postgres -c "CREATE ROLE jenkins_TEST_SU LOGIN PASSWORD 'reallysecurepassword' SUPERUSER" I created the user from psql at command line using this command. In doing this I decided to create a new super user account for Jenkins to use in these cases. Jenkins spool up a test PostgreSQL container and restore the recent backups for me. Is not a backup at all, I decided to have I have a local Jenkins instance that takes backups of a number of PostgreSQL databases. It was a bit more difficult to troubleshoot this time since I wasĮrroneously blaming the issue on being related to running inside a Docker container, which Where I didn't expect so I wanted to document this before I forget what happened. The first time that PostgreSQL has caught me off guard with being Ran into a headache caused by the case sensitiveness of PostgreSQL. By Ryan Lambert - Published July 12, 2015
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |