In our production environment, we separate each shard out into its own
schema to give us flexibility in shard location. This leaves us with a
lot of schemas hosted on a relatively smaller set of servers.
With so many schemas, database migrations started to take a long time
to run across all of the
On Thu, Apr 25, 2013 at 12:17 PM, Tom Lane wrote:
> The cause is that each one will wait for all older snapshots to be
> gone --- and it does that before dropping its own snapshot, so that the
> other ones will see it as something to be waited out too.
This makes sense. Thank you for explaining.
