Thanks. A brief outage seems like the lesser evil.
On Tuesday, January 16, 2018 at 1:06:45 PM UTC-8, Mike Bayer wrote:
>
> even recent PG's seem to still do this:
>
> https://dba.stackexchange.com/a/111092
>
> so your only option other than downtime is to create a new table,
> migrate all the d
even recent PG's seem to still do this:
https://dba.stackexchange.com/a/111092
so your only option other than downtime is to create a new table,
migrate all the data towards it, then drop the old table and rename -
then you'd need to restore additional data you might have lost while
that occurred
Twice recently, on two different PostgreSQL 9.5 databases hosted at Amazon
RDS, we've been unable to apply Alembic migrations. We have successfully
run dozens of Alembic migrations in the past against one of these databases
but those were quieter times for us. As far as I can tell, it's because
