On Wed, Apr 2, 2014 at 1:22 PM, Christopher Jackson <crjackso@xxxxxxxxx> wrote: > > Hi Bricklen, > > Thanks for the feedback. I'll play around with materialized views. My > understanding is they have to be manually triggered for refresh Yep. > and there's an exclusive lock on the view while the refresh is taking place. Is this > your understanding as well? Re-yep. > I'm using PG 9.3.3. If this is true, I'm > curious what clever ways people have come up with to mitigate any issues > with the lock. Kevin Grittner has implemented REFRESH MATERIALIZED VIEW CONCURRENTLY in 9.4. A unique index is needed on the materialized view as well to authorize this concurrent operation. It has the merit to allow SELECT operations on the matview during the refresh. -- Michael -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
