On 31 July 2015 at 15:48, Kevin Grittner <kgri...@ymail.com> wrote: > > Reread the thread.
I stand corrected. > The error is being hit on a VACUUM command > (which is not, of course in any explicit transaction). > Seems like VACUUM only ever needs a read-committed snapshot. Whether it takes a read-committed or repeatable read makes no difference. Does brin_summarize_new_values() need to track what it reads for serializable transactions? -- Simon Riggs http://www.2ndQuadrant.com/ <http://www.2ndquadrant.com/> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
