Lets not forget the column casing issue, you either get columns to match your apps casing and have to quote them everywhere or live with them being lower cased automatically. https://dev.to/lefebvre/dont-get-bit-by-postgresql-case-sens...

Don’t forget “libpq”

Funfact: PQ is short for toilet paper in French So libpq always cracks me up. But then again there's a theorem prover called Coq (which is indeed pronounced as you imagine, it means rooster) and it's been named by French researchers at INRIA!

libcaca, also french: http://caca.zoy.org/

Ok, let's talk about this... pico, the editor and SI prefix, means "dick" in at least some Spanish-speaking countries... Source of endless nerd jokes.

Not to mention the (un)surprisingly low sales in spanish speaking countries of the car known as the Vauxhall Nova ...

As an American, I feel like I have to deliberately mis-pronounce 'coq' the theorem prover like 'coke' the soda.

Same. It really doesn't help that their logo is skin-colored and the shape that it is...

PostgreSQL used to be called Postgres. They renamed it when they added SQL support.

This is true. Many people get confused by the name. I've met several developers who refer to it as "Postgray" or some variation.

Recently I saw "post grayskull" on twitter, that's now my favourite. ;)

I've never heard that before, but I kind of like it. Sounds a bit nicer and is easier to say than 'Post Gress'. I'm still not sure how to pronounce the proper name, when it has 'SQL' as part of it. I think it's 'Post Gress Queue Ell', but it feels… bad.

Renaming would be even worse!

Seems to me that they could safely rename to Postgres without much downside.

Among other potential issues, this would make it much harder to search for information related to the database. Starting out, it'd always make sense to google for eg "postgres ilike", but for new features you'd have to search for eg "NewNameSQL kindalike" (assuming a new ILIKE replacement called KINDALIKE comes along in pg15 aka newname3).

Even years in to the rename, newcomers to NewNameSQL would need to be told that it used to be called Postgres and that they should look for things related to that too.

Tools and code that refer to Postgres would all have to change their names, including those developed internally, open-source, closed-source, and no-longer-maintained. Not all would, and some would change the name and functionality at the same time.

It'd be chaos.

I meant change the name from PostgreSQL to Postgres.

Ah! So sorry for misunderstanding. Yes that sounds like a straightforward, good idea!