3 ms·

I tried out this feature in the Basic tier, but my I see downtime during the scaling up of the instance. I opened a psql console and ran "BEGIN; SELECT CURRENT

I tried out this feature in the Basic tier, but my I see downtime during the scaling up of the instance. I opened a psql console and ran "BEGIN; SELECT CURRENT_TIMESTAMP; SELECT pg_sleep(200); SELECT CURRENT_TIMESTAMP; COMMIT;" I see the error "server closed the connection unexpectedly"

kamathsun 9y ago
The application should have logic to re-try connections. When you scale, there is a brief moment ~30-45seconds when the app wont be able to connect to the database and then resumes if you re-try connection. /I work at Microsoft on the managed PostgreSQL service/
- martinknafve 9y ago
  How do you accomplish no application downtime if for 45 seconds you can't connect to the database? In background processes you might get away with retrying connections for a minute but most users will probably consider your site broken if page load time is 45 seconds.
- GordonS 9y ago
  That's a rather... 'liberal' use of 'no application downtime'.