I know my Dunning Kruger effect is high on this. But why hasnt someone built a MSSQL to PGSQL so you could replace MSSQL with PGSQL and client apps would be none the wiser. (im talking basic queries, not all features) #dev #mssql #pgsql

#PGSQL Phriday #008 https://www.pgsqlphriday.com/2023/04/pgsql-phriday-008/

#PGSQL Phriday #008 invitation - pgMustard https://www.pgmustard.com/blog/pgsql-phriday-pg-stat-statements

Why developers love PostgreSQL by @starbuxman #pgsql
https://youtu.be/fw-SCAJU_5Y

Dites,

Vous avez des astuces pour passer d'une base H2 à PosgreSQL ?

#aide #pgsql

@RogerBW @0xabad1dea #MySQL -> "My Squeal", but then #PgSQL -> "Pig Squeal", #SQLite -> "Squeal-Ite", etc.

@aurynn @xssfox @thomasbeagle @artemai both my #pixelfed and #mastodon instances are docker-compose + env file; #pgsql is on a separate cluster. Not sharing #redis currently (sometime soon). Rest of our cluster is #rtx3080s from a mining rig we aquired for #ml inference.

Sehr interessante Folge zu #Datenbanken allgemein und sprachunabhängig. Viel gelernt.

https://python-podcast.de/show/PostgreSQL-und-MariaDB/

#postgres #pgsql #mariadb #mysql #sql #dbms #nosql #c #cpp #podcast

There isn't much that is similar to a pure joy of using new technology for the first time.

My first insert into an #ecto-powered #pgsql:

#myelixirstatus #postgresql

From 20 Jan: Creating user, database and adding access on PostgreSQL (and automate the process) - https://stackfame.com/creating-user-database-and-adding-access-on-postgresql #pgsql #database

#mastodon is very stable in terms of memory consumption!

But I'm thinking about what we're really doing here in #fediverse and I'm comparing it with, let's say, resource footprint of #circumlunar community (Zaibatsu / ... / Soviet) and realise that their footprint is kind of zero.

Everyone is on one of the three manually federated servers, using UNIX / pre-UNIX tools to communicate with each other, with the only non-UNIX tool being IRC.

Somehow it doesn't take 2GiB of memory and somewhat constant CPU load for #sundogs to exchange bytes.

I get that to host huge instances like mastodon.social, it makes sense to have #pgsql, but it feels like individual instances should be able to be cohosted on the same machine.

I'm committed to explore using file system and files for #doauth persistent storage backend.

But that also brings me to a dilemma of whether or not to use #elixir for the rewrite or to use #rust, to decrease footprint.

Obviously, #elixir will yield more stable, fault tolerant code with easier replication. #Rust, however will reduce excess footprints to 0 at a cost of longer development time (I'll need to benchmark current #tokio-based HTTP servers and see if I need to write my own dead simple server that doesn't use generics / isn't bloated), and it can easily eat up a month of my time.

Maybe it's all non-issue, especially if there's just one BEAM machine launched per host and we plug our applications into it (as intended)...

I think that the fact that I'm heavily leaning towards #elixir as the main production technology even though "close-to-metal" argument is important to me is a clear sign I should use it for production in #doma.

Did anyone experienced slow connection #javascript to #php to #posrgresql. It takes up to 5sec to respond post request and I know it's not the #pgsql because the same query on #pgadmin takes 120ms

@leah sehr sehr kritische Situation innerhalb einer #pgSQL. 1. Storage Snapshot, 2. db dump, 3. https://lxadm.com/PostgreSQL:_ERROR:_invalid_page_header_in_block_13760_of_relation_base/16995/67484 Wichtig ist vorher herauszufinden wozu der korrupte block gehört. Viel Erfolg! Und wie immer: Better have many backups 😉

#PostgreSQL 11 is released https://www.postgresql.org/about/news/1894/

#pgsql