Re: ERROR: found multixact from before relminmxid

On 11/7/18 1:21 PM, Alexandre Arruda wrote: The best solution that I have found is kick all connections and execute a select for update to /dev/null in the affected tables, i.e.: psql -o /dev/null -c "select * from table for update" database After this, the vacuum is executed w/o problems

Re: ERROR: found multixact from before relminmxid

The best solution that I have found is kick all connections and execute a select for update to /dev/null in the affected tables, i.e.: psql -o /dev/null -c "select * from table for update" database After this, the vacuum is executed w/o problems again. Best regards, Alexandre Em qua, 7 de nov

Re: ERROR: found multixact from before relminmxid

On 11/5/18 5:41 PM, Adrien NAYRAT wrote: We "solved" with a dump/restore on another server, also we kept previous cluster to investigate. I want to be sure we encountered the bug solved in 9.6.9 and it is not a new one. FYI, I am not sure I will be able to keep previous cluster many days.

Re: ERROR: found multixact from before relminmxid

On 6/8/18 8:30 PM, Jeremy Finzel wrote:  No I was referring to this from the documentation: Avoid spuriously marking pages as all-visible (Dan Wood, Pavan Deolasee, Álvaro Herrera) This could happen if some tuples were locked (but not deleted). While queries would still

Re: ERROR: found multixact from before relminmxid

On 2018-Jul-13, Sean McIntyre wrote: > Quick correction :) > > I am running PostgreSQL *9.6.8* on AWS RDS. I'm going to try to pg-repack > the table and will look to upgrade to *9.6.9* (though it's not presently > available on RDS). Yay RDS ... -- Álvaro Herrera

Re: ERROR: found multixact from before relminmxid

Quick correction :) I am running PostgreSQL *9.6.8* on AWS RDS. I'm going to try to pg-repack the table and will look to upgrade to *9.6.9* (though it's not presently available on RDS). Sean On Fri, Jul 13, 2018 at 11:14 AM Sean McIntyre < sean.mcint...@warbyparker.com> wrote: > Dear all, > >

Re: ERROR: found multixact from before relminmxid

Hi, On 2018-06-08 13:30:33 -0500, Jeremy Finzel wrote: >Avoid spuriously marking pages as all-visible (Dan Wood, Pavan Deolasee, >Álvaro Herrera) > >This could happen if some tuples were locked (but not deleted). While >queries would still function correctly, vacuum would

Re: ERROR: found multixact from before relminmxid

> > Is there any chance I could get access > to a copy of the data? It's very hard to debug something like this > without something that can reproduce the issue... > It would be very difficult for us to be able to clean and anonymize this data and provide a snapshot publicly. But I am very

Re: ERROR: found multixact from before relminmxid

On Fri, Jun 8, 2018 at 1:08 PM Andres Freund wrote: > On 2018-06-08 12:38:03 -0500, Jeremy Finzel wrote: > > On Tue, Jun 5, 2018 at 8:42 PM, Alexandre Arruda > wrote: > > > > > Em seg, 28 de mai de 2018 às 16:44, Andres Freund > > > escreveu: > > > > > > > > Hi, > > > > > > > > I think I found

Re: ERROR: found multixact from before relminmxid

On 2018-06-08 12:38:03 -0500, Jeremy Finzel wrote: > On Tue, Jun 5, 2018 at 8:42 PM, Alexandre Arruda wrote: > > > Em seg, 28 de mai de 2018 às 16:44, Andres Freund > > escreveu: > > > > > > Hi, > > > > > > I think I found the bug, and am about to post a fix for it belo > > >

Re: ERROR: found multixact from before relminmxid

On Tue, Jun 5, 2018 at 8:42 PM, Alexandre Arruda wrote: > Em seg, 28 de mai de 2018 às 16:44, Andres Freund > escreveu: > > > > Hi, > > > > I think I found the bug, and am about to post a fix for it belo > > https://postgr.es/m/20180525203736.crkbg36muzxrj...@alap3.anarazel.de. > > > >

Re: ERROR: found multixact from before relminmxid

Em seg, 28 de mai de 2018 às 16:44, Andres Freund escreveu: > > Hi, > > I think I found the bug, and am about to post a fix for it belo > https://postgr.es/m/20180525203736.crkbg36muzxrj...@alap3.anarazel.de. > > Greetings, > > Andres Freund Hi Andres, In end of April we did a complete

Re: ERROR: found multixact from before relminmxid

Hi, I think I found the bug, and am about to post a fix for it belo https://postgr.es/m/20180525203736.crkbg36muzxrj...@alap3.anarazel.de. Greetings, Andres Freund

Re: ERROR: found multixact from before relminmxid

On April 10, 2018 11:51:40 PM PDT, Pavan Deolasee wrote: >On Wed, Apr 11, 2018 at 8:31 AM, Alexandre Arruda >wrote: > >> 2018-04-10 19:09 GMT-03:00 Peter Geoghegan : >> > On Tue, Apr 10, 2018 at 4:31 AM, Alexandre Arruda

Re: ERROR: found multixact from before relminmxid

On Wed, Apr 11, 2018 at 8:31 AM, Alexandre Arruda wrote: > 2018-04-10 19:09 GMT-03:00 Peter Geoghegan : > > On Tue, Apr 10, 2018 at 4:31 AM, Alexandre Arruda > wrote: > >> Actualy, I first notice the problem in logs by autovacuum: > >> > >>

Re: ERROR: found multixact from before relminmxid

2018-04-10 19:53 GMT-03:00 Andres Freund : > On 2018-04-10 08:31:20 -0300, Alexandre Arruda wrote: >> 2018-04-09 23:51 GMT-03:00 Peter Geoghegan : >> > On Mon, Apr 9, 2018 at 6:56 PM, Alexandre Arruda >> > wrote: >> >> (... and all other

Re: ERROR: found multixact from before relminmxid

On 2018-04-10 08:31:20 -0300, Alexandre Arruda wrote: > 2018-04-09 23:51 GMT-03:00 Peter Geoghegan : > > On Mon, Apr 9, 2018 at 6:56 PM, Alexandre Arruda wrote: > >> (... and all other indexes returns null too) > >> > >> I tried with bt_index_check too. Same

Re: ERROR: found multixact from before relminmxid

On Tue, Apr 10, 2018 at 4:31 AM, Alexandre Arruda wrote: > Actualy, I first notice the problem in logs by autovacuum: > > 2018-04-10 08:22:15.385 -03 [55477] CONTEXT: automatic vacuum of > table "production.public.fn06t" > 2018-04-10 08:22:16.815 -03 [55477] ERROR: found

Re: ERROR: found multixact from before relminmxid

2018-04-09 23:51 GMT-03:00 Peter Geoghegan : > On Mon, Apr 9, 2018 at 6:56 PM, Alexandre Arruda wrote: >> (... and all other indexes returns null too) >> >> I tried with bt_index_check too. Same results. > > That's interesting, because it tells me that you have a

Re: ERROR: found multixact from before relminmxid

On April 9, 2018 7:51:19 PM PDT, Peter Geoghegan wrote: >On Mon, Apr 9, 2018 at 6:56 PM, Alexandre Arruda >wrote: >> (... and all other indexes returns null too) >> >> I tried with bt_index_check too. Same results. > >That's interesting, because it tells me

Re: ERROR: found multixact from before relminmxid

On Mon, Apr 9, 2018 at 6:56 PM, Alexandre Arruda wrote: > (... and all other indexes returns null too) > > I tried with bt_index_check too. Same results. That's interesting, because it tells me that you have a table that appears to not be corrupt, despite the CLUSTER error.

Re: ERROR: found multixact from before relminmxid

On Mon, Apr 9, 2018 at 5:55 PM, Alexandre Arruda wrote: > I ran amcheck in all index of a table and I only get empty returns. Did you try doing so with the "heapallindexed" option? That's what's really interesting here. -- Peter Geoghegan

Re: ERROR: found multixact from before relminmxid

2018-04-09 18:23 GMT-03:00 Peter Geoghegan : > > On Mon, Apr 9, 2018 at 7:01 AM, Tomas Vondra > wrote: > > The bigger question is whether this can actually detect the issue. If > > it's due to an storage issue, then perhaps yes. But if you only see > >

Re: ERROR: found multixact from before relminmxid

On Mon, Apr 9, 2018 at 7:01 AM, Tomas Vondra wrote: > The bigger question is whether this can actually detect the issue. If > it's due to an storage issue, then perhaps yes. But if you only see > multixact issues consistently and nothing else, it might easily be a >

Re: ERROR: found multixact from before relminmxid

On 04/09/2018 01:49 PM, Alexandre Arruda wrote: > > > 2018-04-06 13:11 GMT-03:00 Tomas Vondra >: > > > > On 04/06/2018 04:29 PM, Alexandre Arruda wrote: > > 2018-04-06 9:39 GMT-03:00 Tomas Vondra

Re: ERROR: found multixact from before relminmxid

2018-04-06 13:11 GMT-03:00 Tomas Vondra : > > > On 04/06/2018 04:29 PM, Alexandre Arruda wrote: > > 2018-04-06 9:39 GMT-03:00 Tomas Vondra > >: > > > > > > > > On 04/06/2018 02:09 AM, Alexandre

Re: ERROR: found multixact from before relminmxid

2018-04-06 9:39 GMT-03:00 Tomas Vondra : > > > On 04/06/2018 02:09 AM, Alexandre Arruda wrote: > > Hi, > > > > Some time ago, I had this errors frequently showed in logs after some > > autovacuum in some tables(pg 9.6). VACUUM FULL or CLUSTER in this tables > > show