Hi,
On 2018-12-28 19:49:36 -0500, Tom Lane wrote:
> Mark Fletcher writes:
> > Starting yesterday morning, auto vacuuming of one of our postgresql 9.6.10
> > (CentOS 7) table's started failing:
> > ERROR: found multixact 370350365 from before relminmxid 765860874
> > CONTEXT: automatic vacuum of
On Fri, Dec 28, 2018 at 4:49 PM Tom Lane wrote:
>
> Yeah, SELECT FOR UPDATE should overwrite the broken xmax value and thereby
> fix it, I expect. However, I don't see anything in the release notes
> suggesting that we've fixed any related bugs since 9.6.10, so if this
> just appeared then we've
Mark Fletcher writes:
> Starting yesterday morning, auto vacuuming of one of our postgresql 9.6.10
> (CentOS 7) table's started failing:
> ERROR: found multixact 370350365 from before relminmxid 765860874
> CONTEXT: automatic vacuum of table "userdb.public.subs"
Ugh.
> Reading the various disc
Hi,
Starting yesterday morning, auto vacuuming of one of our postgresql 9.6.10
(CentOS 7) table's started failing:
ERROR: found multixact 370350365 from before relminmxid 765860874
CONTEXT: automatic vacuum of table "userdb.public.subs"
This is about as plain and simple a table as there is. No
