[hstaab]

Recently, I gave Fly an honest go for a new multi-container project that seemed like a good fit. After digging in, I found that the pg clusters had some sort of system wide bug and couldn’t be attached to any of my apps.

It was a bummer. Everything seemed great, I just literally couldn’t use it.

I’d love to hear others experiences with the PG features. I could see it replacing Digital ocean for my use cases (if it works reliably)

[mrkurt]

I'm sad this bug burned you. We had some brittle infrastructure for talking into a Postgres cluster, and it was a bit of a fire drill to rip it out and simplify. You would have a better experience if you tried today!

We know this because we have metrics on how many people created and then destroyed Postgres DBs without successfully connecting an app to them. When we show this to investors we'll explain that the improvement was a big win for our "go to market efforts". But you should know it was really just a bug fix for something we disappointed you with.

[ontoillogical]

> When we show this to investors we'll explain that the improvement was a big win for our "go to market efforts". But you should know it was really just a bug fix for something we disappointed you with.

That made me chuckle :)

I encountered some of those same postgres issues and so far have been only running a staging database on Fly. This comment is motivation for me to finish moving my real DB over from google.

P.S. I was running my own fork of your postgres container so I could include postgis, and this probably made management even more brittle -- I'm really happy to see https://github.com/fly-apps/postgres-ha/pull/44#issuecomment... landed!

[robertlagrant]

"How we go to market with a cloud"

<Picture of a large desk fan>

[thejosh]

Great, because I also saw this, otherwise fly is great.