Hi Ken,
With that level of dinamism of application servers where there is no way to
keep consistency among them , as you say concurrency must be turned into a
single thread to make sure schema migration will not be locked up by
application threads .
Have you though about constraining connections
> Do you really need to allow web server connections to the database during a
> schema migration ? Why not locking them up either with pg_hba.cong or a
> firewal rule or symply shut it off temporarily ?
So this would be ideal if we could control the situation 100%, to be
clear our software is a sh
Hi Ken,
Do you really need to allow web server connections to the database during a
schema migration ? Why not locking them up either with pg_hba.cong or a
firewal rule or symply shut it off temporarily ?
Cheers,
A.A.
On Fri, Mar 21, 2014 at 10:46 AM, Ken Barber wrote:
> Hi there,
>
> I was j
Hi there,
I was just wondering if anyone has some general advice for how to
ensure a schema migration for an application has exclusivity during
its run.
This is to avoid silly things like, if someone leaves an application
server running during migration the migration should be able to lock
someho
