#Tag
We are excited to welcome LOXODATA as a Partner sponsor of pgDay Paris 2026! We could not run this event without our sponsors.
We are excited to welcome LOXODATA as a Partner sponsor of pgDay Paris 2026! We could not run this event without our sponsors.
anybody wanna recommend me a favorite way of remotely managing a #Postgres server (you know, create/delete databases, database users etc) which doesn't involve me vastly increasing the attack surface of said server?
major bonus points if it has any awareness / ability to deal with #PgBouncer.
anybody wanna recommend me a favorite way of remotely managing a #Postgres server (you know, create/delete databases, database users etc) which doesn't involve me vastly increasing the attack surface of said server?
major bonus points if it has any awareness / ability to deal with #PgBouncer.
Spent the last couple days brushing up on web dev, specifically data back and forth / forms.
3 nodes (db, backend, frontend) -> 2 edges = double edge case.
Piping data back and forth, with 1 node being unknowable + error communication is damn complex!
I'm a Senior #Software Engineer with 20+ years of professional experience.
I have primarily worked with web technologies such as #JavsScript, #HTML, #CSS, #nodejs, and #typescript.
My last job was as a Senior #React Engineer.
I've worked with #Postgres, #MySQL, and #MSSQL databases.
Backend tech includes C#, Go, PHP, and ASP.
Countless projects ranging from SPAs to $100 million ecommerce sites to enterprise level software.
I'm a Senior #Software Engineer with 20+ years of professional experience.
I have primarily worked with web technologies such as #JavsScript, #HTML, #CSS, #nodejs, and #typescript.
My last job was as a Senior #React Engineer.
I've worked with #Postgres, #MySQL, and #MSSQL databases.
Backend tech includes C#, Go, PHP, and ASP.
Countless projects ranging from SPAs to $100 million ecommerce sites to enterprise level software.
spent most of today scrubbing about with #postgres #prisma and #sveltekit, and learnt a lot and now I'm mentally tired but physically understimulated and going for a run bye
I've learned more about #postgres vacuuming too.
OTOH, it would be better if fediverse admins didn't have to do any maintenance on their database at all. Having to do so makes it much harder to self-host, and this in turn both reduces the size of the #fediverse and makes the UX worse.
Database collates are ridiculous. Why would I want to globally configure a database's ordering rules? Either I care about presenting locale-appropriate orderings, in which case I need that to be configured PER APPLICATION USER, or I don't care, in which care just use whatever makes the most sense for performance/simplicity (probably ordering by byte value). I don't understand the use case for database-global collate settings. #postgresql #postgres#mysql #databases #rdbms #programming
Database collates are ridiculous. Why would I want to globally configure a database's ordering rules? Either I care about presenting locale-appropriate orderings, in which case I need that to be configured PER APPLICATION USER, or I don't care, in which care just use whatever makes the most sense for performance/simplicity (probably ordering by byte value). I don't understand the use case for database-global collate settings. #postgresql #postgres#mysql #databases #rdbms #programming
I've used #MySQL before (last time was 2016, I think), but today I'm mostly onto #Postgres (and sometimes, #SQLite). I know PG is superior to MySQL is pretty much all aspect I could think of, but still, it seems that MySQL still has a quite big user base.
What's the catch? What am I missing here? Why would someone use MySQL over Postgres to build smt since Postgres [apparently] is better than MySQL in every single possible aspect?
It's a honest question. Please help me understand it – and perhaps, consider modern MySQL/MariaDB in next projects. :)
Install and run a PostgreSQL database locally on Linux, MacOS or Windows. PostgreSQL can be bundled with your application, or downloaded on demand.
This library provides an embedded-like experience for PostgreSQL similar to what you would have with SQLite.
So I split responsibilities:
- privateId: a sequential bigserial, used only for db internal references
- id: a prefixed Nano ID like us_msny03yjrocv, used everywhere else
The prefix (e.g. us_, ag_, dn_) reveals the entity type. The rest is short, unambiguous, and random.
This setup delivers the best of both worlds:
- Fast joins and cache-friendly indexes
- Opaque, secure public IDs with great DX
No need to compromise.
News includes EEF's first #CVE release, Supabase's Multigres for scaling #postgres, new #MCP servers for Phoenix, #Erlang surviving extreme load tests, LiveDebugger v0.3.0 preview, and more! @elixirlang#ElixirLanghttps://www.youtube.com/watch?v=DsVyY4XHVm8
News includes EEF's first #CVE release, Supabase's Multigres for scaling #postgres, new #MCP servers for Phoenix, #Erlang surviving extreme load tests, LiveDebugger v0.3.0 preview, and more! @elixirlang#ElixirLanghttps://www.youtube.com/watch?v=DsVyY4XHVm8
Today it crossed my mind for the first time that, after all, I don't need #typescript at all.
Some months ago, after some months spent with #rust I got to a compromise idea that I should use #rust for "serious" tasks, and #javascript for quick modelling. The idea evolved quickly into it's same form, but with #typescript in place of JS.
Two months later I'm failing to get #deno run my software because the network layer won't work if I import some .ts file of mine; if only I knew which one.
in the meantime I got much braver with #rust, I love the syntax, the tightness, it's got a great native #postgres driver https://github.com/sfackler/rust-postgres (can pipeline requests, while I found 0/zero/ ts drivers capable of doing the same so I had to revert to good ol' JS https://github.com/brianc/node-postgres...)
So, tomorrow is a new day, we'll see...
We are excited to welcome LOXODATA as a Partner sponsor of pgDay Paris 2025! We could not run this event without our sponsors.
A space for Bonfire maintainers and contributors to communicate
