PostgreSQL

“NextJS/Shadcn web app, postgres db, eve agent layer”

“We run Postgres when we host our banking / financial stuff”

“we run Kubernetes workloads where we have 20-30 or sometimes more pods connecting to a single Postgres instance”

“against a single postgres-based backend without any cleanup between tests”

“it's multitudes of magnitude quicker than postgres for most general use cases.”

“it can also connect directly to Postgres. For our data warehouse at a medium sized newspaper”

“If your data and workloads live on standard Kubernetes with Postgres, object storage and the usual Prometheus/Grafana/Loki”

“It needs a vault cluster, dynamic PostgreSQL users take years to get right”

“everything I've read about people using it in prod tells me that most organizations never really grow beyond requiring anything more than what it offers.”

“IME, setting random_page_cost to 1.1 is more likely to produce good results overall”

“We tried to get as much mileage as we could out of Postgres before we switched to clickhouse and it was night and day.”

“We switched our main API from Postgres to Turso last month and haven't looked back.”

“Have effectively been using these to implemnt + learn so much about Postgres”

“running fairly large self-hosted HA PostgreSQL databases in production”

“I have a colleague that's incredibly strong with databases (we use a mix of MySQL and PostgreSQL)”

“I've worked at orgs that used Postgres in production, but I've never been the one responsible for tuning/maintenance.”

“speaking as a DBRE who has used both MySQL and Postgres, RDS and Aurora in production”

“maybe an hour of downtime yearly as we upgrade Postgres to a new version.”

“To prevent cross-test leakage we wrap each test in a BEGIN..ROLLBACK, and transform inner use of transactions to save points in our db client layer.”

“we licensed the Telerik UI components. We ended up dropping them, but not until we had initiated a migration to Java/PG”

“Of course, everything has it's place and we run those too”

“table-specific Postgres roles for audit logs and dynamically provisioned databases per-clinical-trial”

“it's a home-grown distributed system that's built on top of Postgres and Cassandra with a whole control plane and data plane.”

“We run ours as a container service within the development environment that will compile your code from a postgres dump file.”

“automate dumping data from an on-prem PGSQL server to a cloud bucket.”

“For example, we have Postgres in the catalog today. When we rebuild, we have some tests that run with various configurations”

“It was a simple Node.js + PostgreSQL server running on a fire-walled on-premise machine. We let it run untouched for just over two years.”

“This is all of the code needed to use Postgres in prod and PGLite in test/dev”

“we want to be able to swap between SQLite, postgres and mySQL.”

“we can build on WSL with just some small changes to an env file because we run a psql container”

“We migrated from postgres to ADX based on cost analysis done of the managed version on Azure.”

“We replaced it with postgres+timescale on one average server.”

“We had a Django application backed by PostgreSQL, which we migrated to CockroachDB using their official backend.”

“We use it for quickly spinning up a temporary postgres instance to run our db tests against.”

“I'm working on a project that has ~22,000 tests that operate on Docker container of the same version of Postgres used in production.”

“Really fast to spin up a temporary postgres instance”

“We mostly serve web requests, talk to a PostgreSQL database”

“sync data into a Postgres database as JSONB... we leverage materialized views and trigger-based optimistic locking”

“At the moment it's a non-starter because we use pg views to shape the data for the frontend.”

“All my experiments with a 3 worker postgres cluster showed that if the node count is less than 3”

“I went through a postgres 10 > 16 upgrade recently. What made it easier was just doing a test run of the upgrade process.”

“everything in prod still works on plain ol redis and Postgres”

“the type of PostgreSQL service we use is being retired.”

“I led a project at a startup to move from Postgres to Elasticsearch for geographic search.”

“I haven’t done it in prod, but I made a PoC.”

“so we switched back to postgresql included with vercel. Turns out that was neon under the hood.”

“we've switched over our staging database ... I got to talk to someone who was intelligent about Postgres”

“Database is as aged Postgres cause that's all that is really important.”

“a postgres database”

“how are your security teams ok with exposing your PG server to the internet, relying mainly on RLS?”

“Yes, use sqlite locally for development and run PG in prod.”

“I'd use the PG catalog tables directly.”

“as we run our Postgres database in docker the FS latency makes for a noticeably slower dev environment.”

“Postgres has very subtly different sort ordering when we use the alpine based images.”

“I've been using Hasura generally with vanilla Postgres DBs”

“I'll often have integration tests that swap out some adapter (e.g. the postgres-users-repository, for the memory-users-repository”

“This is not easy to do with PostgreSQL, which we use for all other scenarios requiring a DB.”

“What we do is much of the business logic in Postgres (triggers, constraints, etc).”

“Migrating from Go to Rust... Rust web service communicating with the usual suspects; Postgres, RabbitMQ, etc.”

“PG can also do JS or Py stored procedures but you get a better developer experience if your logic code is deployed through regular CI/CD”

“the replication slots that we use to synchronize with other services (e.g. data warehouse)”

“my choice was based entirely on the fact that I already use postgres”

“We use a custom trigger to build an event log in Postgres. We actually found it more straightforward to use this approach than to use the WAL packages we considered.”

“Still, the performance degradation even in development is quite impactful.”

“We use MySQL more often than Postgres; I may take a stab at creating something similar for MySQL.”

“we use Cassandra for example, so there is a "foreign key" usually from a PG row to a Cassandra row”

“exposes the standard environment variables to configure a Postgres client.”

“At Notion we run ~100 Postgres instances and we're pretty far off from being Fortune 500”

“We've run the implementation for several years across a few hundred tables for an ERP product.”

“I mean this is more of less what using a local container for Postgres is.”

“In the end we switched back to postgres + redis because it was cheaper.”

“I never ran postgres in prod in k8s, but i used cloudnative-pg for some light, non-critical loads, dev/stg stuff.”

“About 5 years ago we migrated to postgres and installed pgBouncer because of course you do.”

“very excited at the potential features a custom postgres proxy can unlock.”

“One source of truth for connectors (google drive / sheets, slack, postgres database aggs)”

“we've run the tests against in-memory db and production was postgres. Of course there was a bug caused by different SQL implementations.”

“I'll build the statistics in our postgres data warehouse and use a little ruby script I wrote to push them from postgres to Dynamo”

“I work for public institutions, and I use Postgres, not Oracle.”

“we use a version of postgres that does not support it - but I see now that it can be useful”

“connecting privately in production to a Postgres managed database on DigitalOcean”

“we were already using Postgres in our backend so we wanted to store this data in there as well”

“it's not terribly hard to add efficient count tracking that works with this implementation of MVCC, using row triggers. I use it often in production.”

“just plain old running that postgres in production in a VM provided by your vmware esx cluster”

“Supabase is just Postgres, we don't run any forks. We run vanilla PostgREST too (behind a proxy)”

“eventually learned to just use the tools I knew (react, node, postgres)”

“back when we switched databases from mysql to postgresql. ...push it into a postgres in a container.”

“Our stack is (per country) 3 nodejs services, PostgreSQL, redis and some frontend services.”

“We still had a DBA for the Postgres stuff”

“we run the infrastructure for thousands of projects/backends which we have absolutely no control over”

“we're going to move to only one Postgres cluster with multiples db inside”

“We are using paid dynos but free tier redis and Postgres.”

“We're using `Phoenix.Tracker` to globally distribute the Erlang PIDs of all of our Postgres connections.”

“My mid-sized shop uses managed offerings for MySQL and Postgres but we run several stateful workloads”

“we run our postgres database on a massive bare-metal dedicated server running FreeBSD”

“RDS for postgres.”

“We deal with payloads that are just a little too big for a database (we run Postgres and Clickhouse)”

“we have a few Spring Boot based webapps which were running (along with PgSQL) on a shared AWS t2.medium instance”

“we transitioned to pure PG”

“installing Postgres on MacOS vs Linux) so there's lots of little learning curves.”

“Postgres as the database.”

“then I use hosted Postgres in prod.”

“For postgres failover switch to new master required about 1-2 minutes of downtime”

“politics were involved in producing a local schema that we could load into Postgres on Compose.”

“we built a tool for managing postgresql databases with nix.”

“when we migrated it into a UTF-8-configured Postgres database, some of the UTF-8 characters were silently corrupted”

“I run Postgres in prod so I can use purely random UUIDv4”

“Each site has a separate pg db and everything is glued together / configured / deployed via ansible.”

“it's not easy to inspect or fix data in production the way we would with postgres.”

“triggers in Postgres fire off containers to process those areas and fill in contents of other layers.”

“for our codebase, we run transactions against the database in most of the integration tests.”

“Postgres/Elastic for storage (depending on the balance performance/flexibility)”

“We run high-availability Ceph, Postgres, and Consul, across 3 Hetzner DCs”

“Been using postgraphile on postgres as a backend lately, but I don't think anyone would describe sql as fun.”

“we would have had better availability if we had avoided adding the temperamental rabbitmq cluster and instead implemented the job queue in our non-HA postgres instance”

“one component per type of source data (postgres, XLSX files, XML)”

“Better product due to beefing up the Postgres clusters with part of the savings.”

“We've migrated a major social network from PG onto our MySQL-based platform and our MySQL DBAs didn't even notice.”

“I seriously trialled and compared Postgres vs MySQL at the start of a major major project”

“I've managed shards/clusters of Postgres and MySQL in my life”

“I regularly run PostgreSQL in production, but I can use SQLite as an in-memory database for unit tests”

“Development is usually done on SQLite and staging / production on Postgres.”

“I've since ported a few apps in early development or production between Microsoft SQL server, MySQL and Postgres”

“The DB pods push their WALs to S3 and I have script to spawn a new PG from S3 using PITR.”

“we need to migrate from heroku postgres to aws rds postgres”

“I've only ever seen PostgreSQL/MySQL/MariaDB/Oracle be deployed successfully as single instances in prod that are scaled vertically”

“Postgresql, Redis and Docker Compose.”

“Having said this, I just installed PostgreSQL last week, hehe.”

“on Monday we moved to Postgres 13.3”

“retrieving a JSON string from the postgres query, then interpolating it into a boilerplate string response.”

“Postgres was our first internal application for private networks.”

“We switched to Cloud SQL from running our own Postgres and it is a huge improvement”

“RDS (MySQL or PostgreSQL), ES (OpenDistro), S3 (Minio), and SES”

“we had to recreate the functionality of temporal_tables as a PostgreSQL function, rather than extension.”

“We migrated most of our customers over to Red Hat and Postgres (from OpenServer/Informix)”

“we currently depend on go-swagger, SQLBoiler (PostgreSQL) and echo.”

“We migrated a medium-to-large (in terms of model complexity, not rows), from PG to CR about a year ago.”

“I workaround it by publish the Postgres port in "host" mode instead of the default of "ingress" mode”

“I'm using this in production for our core Postgres database and am quite happy with it.”

“We take proven tools like Postgres, and we make them as easy to use as Firebase.”

“We use them in production at Splitgraph to power our DDN... We make a PostgreSQL-compatible endpoint available to the public”

“My company migrated our ~2TB postgres db from heroku to AWS”

“I'm in the process of migrating PostgreSQL to k8s myself and would like to hear your opinions”

“PG is deployed but not under Nomad, mostly just from laziness.”

“we run ANALYZE on our Postgres RDBMS at each deployment”

“It's Postgres under the hood.”

“using the DO's Postgres cheapest plan (still pretty expensive imo)”

“and then about a year into developed we switched to Postgres. It also had a phase where we ran SQLite in development environments”

“had to migrate from PostgreSQL 9.6 to 11 with the release of GitLab 13, and that was planned.”

“We run postgres and redis (keydb) with 3 replicas each with at least one in sync replication”

“We've found numerous bugs in gcc, clang and postgres by building / testing with unreleased compilers.”

“Right now we are pulling a postgres:10 container down from our ECR on every run so definitely some low hanging fruit around that.”

“we switched from doing exercises in MySQL to PostgreSQL when recursion came up”

“We use Postgres instead of a custom”

“I use Postgres, which has a fairly rich set of possible schema objects... I'm typically only dealing with a few dozen schema changes (in production) a year”

“never expose the core tables if possible, and only expose views... fire for all tables”

“I'm very familiar with both (and we use both)”

“it's the main database we use along with Lambdas”

“we can tune the configuration for postgres and memcached to allocate resources in an appropriate way”

“On my own laptop I've found it to be maybe 85% or so as quick as normal single mode Postgres.”

“it's a bit sad having PostgreSQL and not being able to take full advantage of it.”

“I have 15+ years of Postgres DBA experience”

“In the end we replaced it with a JVM server and a Postgres database.”

“That's why we switched years ago. Going from single CPU to multiple ballooned the costs so much that it was economically viable to do the work to port everything to Postgres.”

“we run hundreds of PostgreSQL database clusters on Kubernetes (on AWS)”

“we replaced a 6 node r4.4xlarge 4TB cluster with a single t2.medium Postgres instance”

“We run the infrastructure in the cloud (we run it on GCP using Postgres and k8s”

“I've been given js+mongo apps by partners that I had to modify to use standard postgres before becoming responsible for herding them in prod.”

“Now, we use Linux alpine docker containers, use postgre instead Sql Server”

“A small Kubernetes cluster and hosted Postgres does not cost much there and is very easy to setup.”

“things sitting behind rancher, postgres, mysql”

“Spin up a fresh Postgres instance on Docker using -P to claim an available ephemeral TCP port”

“Databases are PostgreSQL in AWS RDS with Liquibase used for migrations.”

“our approach with the proxy which... didn't actually serve Postgres data to the users until 'the big switch'”

“I've had undiscovered bugs caused by using a different version of postgres locally in test to the one in prod”

“which uses a Rust microservice backed by a Postgres database.”

“We have an existing production system that uses a combination of SQS, DynamoDB, and Postgres, and EC2s”

“we only moved to an on-prem PostgreSQL instance”

“We've replaced an old "ETL" using a bunch of hard to maintain scripts to mysql_fdw and some materialized view.”

“We are currently using it for the spatial database.”

“I recently tried Postgraphile on an existing postgres database”

“We've been using Postgres on RDS for years and were considering moving to Aurora.”

“Heroku have a fantastic backup system for Postgres, it has already paid for itself.”

“Having ran MySQL in prod for a decade and PostgreSQL in prod for half a decade”

“I am writing one that turns Postgres into one of my own for kicks”

“The "important" events for data science are still stored on postgres”

“i'm "stuck" with VM running postgress and replication with repmgr and barman”

“a traditional Ruby/PostgreSQL/REST api back-end.”

“our app... runs on several TB of PostgresSQL data”

“we harvest these Redis Strings into object storage (both NAS and S3 endpoints) with Postgres storing the metadata to facilitate querying this.”

“what is the latest date (as a UNIX timestamp) you can store in a regular postgres integer column”

“other platforms like postgres have acknowledged that the idea of storing JSON has its merits”

“entity framework core with npgsql”

“Golang, Postgres, Bootstrap + whatever JS I can hack into it abusing the hell out of template/html.”

“we're using postgres schemas, so I need to switch to the correct account before querying for the token”

“put in my postgresql (app db).”

“Right now, we have a 40 vanilla PostgreSQL instances running on ZFS on Linux and a single Citus master node.”

“I'd be extremely dubious of this approach, as I've been burnt before by switching things between dev and prod (like using SQLite in dev, Postgres in prod).”

“causing postgres to go into read-only mode”

“We run Mongo side by side with PG, and even though the PG is just replicated and not also sharded”

“it was a Rails 3 app using Postgres and Elasticsearch that we migrated”

“most of the computation time is spent in json and in Postgres.”

“trying to create a similar setup on real hardware for enterprise customers using pg, pgpool2 and haproxy is already a pain”

“The backend runs on Rails + PostgreSQL”

“We run a sharded+replicated mongo cluster and a redundant postgresql array in docker containers.”

“we run Postgresql in production on Intel and Samsung "data center grade" SSDs”

“For database we use postgresql.”

“a PostgreSQL container for development - we aren't planning to migrate the production databases to Docker anytime soon”

“not connecting to my developement PostgreSQL over a unix domain socket.”

“my expanded and frankly bloated .psqlrc”

“We'd also lose all of the uniqueness constraints that we use in Postgres.”

“we designed a versioning system based closely on Git, but built on Postgres directly.”

“The last site I worked on consisted of nginx, elasticsearch, logstash, kibana, postgresql, celery, redis”

“You still have to have redis, postgresql, and whatever other system dependencies installed.”

“My only 2 complaints are that Postgres and zeroMQ drivers are 3rd party extensions.”

“we're mostly using symfony2 and postgresql”

“We also store the unstructured part of the data in a column that can be queried via json_extract_path_text.”

“we run a very vanilla Postgres setup on big, beefy servers and scale resources vertically”

“we run ZFS as a backend for Postgres all over our public cloud”

“ensure that all strings coming in from Postgres were properly tagged with encodings.”

“we use LAPP (PHP, Postgres) with Laravel, Backbone - also with Redis for caching.”

“I've been using data-only containers to mount directories into these app containers (i.e. Redis and PostgreSQL).”

“As someone who's been using PostgreSQL for over 10 years now, nothing comes close.”

“our current only implementation is PostgreSQL”

“We had to change a few things moving from mySQL to Postgres.”

“I'd love to use PostgreSQL but we don't have resources to manage a decent replica set installation”

“The account management and billing web app is Clojure + Postgres, proxied through nginx.”

“the ecosystem has supported all of our needs: Postgresql, redis, rest, soap, 0mq, AWS”

“We run a pretty standard setup with ELB, Postgres (master/replica), webservers and job processing servers.”

“would absolutely like to extend that to our Postgres DBs.”

“We decided not to use docker containers for our postgres DB in production”

“since we standardized on PostgreSQL (moving off MSSQL) we've been devving on 9.2/9.3”

“I generally use MySQL or PostgreSQL on RDS (AWS) given DBA's are hard to find.”

“a whole bunch of ansible scripts to setup checks for postgres, nginx, etc.”

“to load balance between our Postgres servers”

“I switched to RDS from managed Heroku DBs at that point”

“Do you have a monitor on your PG boxen? I've got them set to warn at 50% full”

“(and Postgres, for search, index, and UI)”

“This was even before we switched to Postgres.”

“I used to have 1000 concurrent writes to my Postgres db. Obviously this had a negative impact on performance”

“now we just use Postgres, MySQL, MongoDB, etc. etc.”

“Erlang, haproxy, rabbitmq, redis, postgres, cassandra, chef”

“Yep, postgres has all the account / user details, lists of what network and channels to join, billing etc.”

“PgREST was originally designed for a large, in-production Postgres app (i.e. Socialtext)”

“In practice tough, we use PostgreSQL, and we don't have any control over how Postgres reads its pages.”

“the psycopg2 calls to PostgreSQL take about 100ms to retrieve the associated data once I've found my search results with Whoosh.”

“We then load those events from S3 into Redshift and Postgres.”

“Postgres/Redis/JVM all running on the same machine, as well as Vagrant”

“We moved to Postgres when we passed 1600 posts/day.”

“moved all of the counters to an in-memory aggregator that flushed to Postgres a couple of times a second.”

“We switched out to Python/PostgreSQL as to be honest it was getting expensive”

“We just completed our migration from Oracle DB to Postgres.”

“Currently we run our Postgres instances on EC2, but are looking to move to get better IOPS.”

“We run both massive SQL server and postgres installations.”

“take a copy of each database VM we run, test apply the upgrade and verify everything works correctly”

“We run PostgreSQL and use its built in streaming replication.”

“installing mysql because we only used postgres before”

“using Postgres features such as UUID fields and fulltext search”

“We already have 25 Linux machines and a few postgres machines in production.”

“At my current job we use PostgreSQL and MySQL in production, and H2 in development.”

“We use PostgreSQL and Cassandra.”

“At Instagram we use PostgreSQL, Redis, and Cassandra.”

“Still Postgres (with Slony, multiple clusters), Redis, Memcache, and some Cassandra for newer things”

“btw, they finally implemented kernel pthreads in the last release, so, our postgres...))”

“significantly meatier servers for our backends running PostgreSQL/Solr/Redis.”

“The first iteration of our storefront was built using a 31 line chef recipe, rails, spree, nginx, unicorn, and postgresql.”

“Joe has been very generous with helping me wrap my head around postgresql.”

“There are many of us here who are running postgres in production already”

“At my company, we use MongoDB, Postgres, Redis, and Solr”

“usually when we run into problems, it's a new version, not an old one.”

“We run far bigger PostgreSQL DBs than this, and we've never had a RHEL crash. Ever.”

“we replaced sixteen extremely beefy postgres slaves with four commodity solr boxes”

“We are already using PostgreSql and Mongodb as as a data storage”

“We use user-defined functions in Postgres, and I have the same complaint”

“we use postgresql, and this happends in a single db transaction”

“At Yammer we use Postgres, Vertica, Redis, Riak, and Memcache.”

“We're a postgres shop and the problem we've run into lately is just the sheer number of open connections to the DB.”

“We use a similar technique for our site together Postgresql. We have our own Software ODBA that writes SQL, marshals the data and puts the marshaled Data into the PGsql-DB.”

“we make use of the latest features of PHP and of our database (constantly running latest Postgres)”

“database: Postgresql”

“we wanted to test on the db we used (postgres) rather than sqlite, so we made a VM”