3 ms·
First, postgres really is great. The few things I'll list here do not make me willing to replace it with something else, however: 1. Tooling is not on par with
by fiedzia 10y ago
First, postgres really is great. The few things I'll list here do not make me willing to replace it with something else, however:
1. Tooling is not on par with other databases. If you want nice GUI that holds your hand and does everything with one click - you may find offer for postgres lacking here. I don't care much about that, but some people do.
2. There is no "in memory" storage (but you can use in memory fs to get the same effect).
3. Extensions often define their own operators (that's good), which are made of some combination of +-*/>=~!@#%^&|`?. Yes. Your code may look like its perl. You can make "select foo @@>&!|~ bar from baz" to be valid query.
4. Finding hosting for postgres in not a problem, but its not something as universal as mysql.
Overall, it really is solid database. I've never been disappointed by postgres, while mysql is always a walk through a forest of wtf for me.
- stray 10y ago2. There is no "in memory" storage (but you can use in memory fs to get the same effect). # Wouldn't this work? fsync=off synchronous_commit=off full_page_writes=off bgwriter_lru_maxpages=0
- fiedzia 10y agoHm, I've never tried that, might work. I've needed this for running tests, where I really don't care for reliability, so I've just set tablespace on ram fs. Creating new files would still cause fs writes, but it might not be an issue.
- lastofus 10y agoI believe data would still be written out to disk (unreliably) during checkpoints with this config.
- anarazel 10y agoUnless you define the tables as unlogged. In that case they'll only be written to disk on a regular shutdown and/or if there's not enough space in shared buffers.
- smt88 10y ago> If you want nice GUI that holds your hand and does everything with one click - you may find offer for postgres lacking here DataGrip, DBeaver (free), HeidiSQL (free)