Fly PG stuck in default_transaction_read_only = ON;

1

We have a fly pg app that is stuck in read only mode - we have tried everything possible.

default_transaction_read_only will always be ON even after:

ALTER SYSTEM SET default_transaction_read_only = OFF;
ALTER DATABASE database_name SET default_transaction_read_only = OFF;

I have a feeling the app hit 90% usage on the volumes which have now been expanded.

We even tried forking to a whole new DB but we are still stuck, can someone please help?? Very frustrating experience.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

4

What do your fly checks list say?

Also, can you paste the output of fly images show ?

There’s a readonly.lock file that gets set during specific situations. You can manually clear it by ssh’ing into the Machine and doing the following:

su postgres
cd ~
rm readonly.lock

If your running an older version, it’s possible you’re hitting a bug. If that’s the case, you should consider updating to the latest version with fly image update.