pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed(no subject)
4+ messages / 3 participants
[nested] [flat]
* (no subject)
@ 2013-11-15 09:16 Karl Hafner <karl@scoreloop.com>
2013-11-15 09:33 ` Re: Karl Hafner <karl@scoreloop.com>
2013-11-22 15:18 ` Re: Alvaro Herrera <alvherre@2ndquadrant.com>
0 siblings, 2 replies; 4+ messages in thread
From: Karl Hafner @ 2013-11-15 09:16 UTC (permalink / raw)
To: pgsql-admin
Dear mailing-list,
I am currently worried about an error that shows up in our log files since
a few weeks:
2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR: MultiXactId 2683601542 does
no longer exist -- apparent wraparound
2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT: automatic vacuum of table
"scoreloop.public.gamer_device_sightings"
It seems that "autovacuum" is active on that table, but it seems to have
restarted today in the morning:
select query_start, query, state, pid from pg_stat_activity where query
LIKE 'autovacuum%' ;
XXX=# select query_start, query, state, pid from pg_stat_activity where
query LIKE 'autovacuum%' ;
query_start | query
| state | pid
-------------------------------+----------------------------------------------------------------------------------+--------+------
2013-11-15 07:13:13.281202+00 | autovacuum: VACUUM ANALYZE
public.gamer_device_sightings (to prevent wraparound) | active | 4360
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re:
2013-11-15 09:16 (no subject) Karl Hafner <karl@scoreloop.com>
@ 2013-11-15 09:33 ` Karl Hafner <karl@scoreloop.com>
2013-11-16 20:25 ` Re: =?ISO-8859-2?Q?Strahinja_Kustudi=E6?= <strahinjak@nordeus.com>
1 sibling, 1 reply; 4+ messages in thread
From: Karl Hafner @ 2013-11-15 09:33 UTC (permalink / raw)
To: pgsql-admin
Sorry, dear mailing list, somehow my email got sent before I finished it :-(
I will go on and repeat. Please bear with me!
I am currently worried about an error that shows up in our log files since
a few weeks:
2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR: MultiXactId 2683601542 does
no longer exist -- apparent wraparound
2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT: automatic vacuum of table
"scoreloop.public.gamer_device_sightings"
It is always the same MultiXactId.
It seems that "autovacuum" is active on that table, but it seems to have
restarted today in the morning:
select query_start, query, state, pid from pg_stat_activity where query
LIKE 'autovacuum%' ;
# select query_start, query, state, pid from pg_stat_activity where query
LIKE 'autovacuum%' ;
query_start | query
| state | pid
-------------------------------+----------------------------------------------------------------------------------+--------+------
2013-11-15 07:13:13.281202+00 | autovacuum: VACUUM ANALYZE
public.gamer_device_sightings (to prevent wraparound) | active | 4360
There are a few locks on tat table:
# select c.oid,c.relname,l.pid,l.mode,l.granted from pg_class c join
pg_locks l on c.oid=l.relation where l.pid='4360' order by l.pid;
oid | relname | pid | mode
| granted
-------+------------------------------------------+------+--------------------------+---------
19862 | index_gamer_device_sightings_on_gamer_id | 4360 | RowExclusiveLock
| t
19719 | gamer_device_sightings_pkey | 4360 |
RowExclusiveLock | t
19309 | gamer_device_sightings | 4360 |
ShareUpdateExclusiveLock | t
The error I described seems to terminate the auto vacuum process: It has
never finished on that table.
It is the only table without a finished vacuum. So I guess the above error
is the reason for this.
Is there anything that I can do to get that fixed? Should I worry about the
error? (I would not if the vacuum would run through).
Any tips, any help would be much appreciated!
Thank you very much! And sorry once more for my posting mistake
Karl
On Fri, Nov 15, 2013 at 10:16 AM, Karl Hafner <karl@scoreloop.com> wrote:
> Dear mailing-list,
>
> I am currently worried about an error that shows up in our log files since
> a few weeks:
>
> 2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR: MultiXactId 2683601542 does
> no longer exist -- apparent wraparound
> 2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT: automatic vacuum of table
> "scoreloop.public.gamer_device_sightings"
>
> It seems that "autovacuum" is active on that table, but it seems to have
> restarted today in the morning:
>
> select query_start, query, state, pid from pg_stat_activity where query
> LIKE 'autovacuum%' ;
>
> XXX=# select query_start, query, state, pid from pg_stat_activity where
> query LIKE 'autovacuum%' ;
>
> query_start | query
> | state | pid
>
> -------------------------------+----------------------------------------------------------------------------------+--------+------
> 2013-11-15 07:13:13.281202+00 | autovacuum: VACUUM ANALYZE
> public.gamer_device_sightings (to prevent wraparound) | active | 4360
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re:
2013-11-15 09:16 (no subject) Karl Hafner <karl@scoreloop.com>
2013-11-15 09:33 ` Re: Karl Hafner <karl@scoreloop.com>
@ 2013-11-16 20:25 ` =?ISO-8859-2?Q?Strahinja_Kustudi=E6?= <strahinjak@nordeus.com>
0 siblings, 0 replies; 4+ messages in thread
From: Strahinja Kustudić @ 2013-11-16 20:25 UTC (permalink / raw)
To: Karl Hafner <karl@scoreloop.com>; +Cc: pgsql-admin
If autovacuum doesn't want to finish the vacuuming of that table, why not
just kill the autovacuum process on that table (you could use
*pg_cancel_backend()*)and run vacuum manually on that table?
Strahinja Kustudić | Lead System Engineer | Nordeus
On Fri, Nov 15, 2013 at 10:33 AM, Karl Hafner <karl@scoreloop.com> wrote:
> Sorry, dear mailing list, somehow my email got sent before I finished it
> :-(
>
> I will go on and repeat. Please bear with me!
>
>
> I am currently worried about an error that shows up in our log files since
> a few weeks:
>
> 2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR: MultiXactId 2683601542 does
> no longer exist -- apparent wraparound
> 2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT: automatic vacuum of table
> "scoreloop.public.gamer_device_sightings"
>
> It is always the same MultiXactId.
> It seems that "autovacuum" is active on that table, but it seems to have
> restarted today in the morning:
>
> select query_start, query, state, pid from pg_stat_activity where query
> LIKE 'autovacuum%' ;
>
> # select query_start, query, state, pid from pg_stat_activity where query
> LIKE 'autovacuum%' ;
>
> query_start | query
> | state | pid
>
> -------------------------------+----------------------------------------------------------------------------------+--------+------
> 2013-11-15 07:13:13.281202+00 | autovacuum: VACUUM ANALYZE
> public.gamer_device_sightings (to prevent wraparound) | active | 4360
>
>
> There are a few locks on tat table:
>
> # select c.oid,c.relname,l.pid,l.mode,l.granted from pg_class c join
> pg_locks l on c.oid=l.relation where l.pid='4360' order by l.pid;
> oid | relname | pid | mode
> | granted
>
> -------+------------------------------------------+------+--------------------------+---------
> 19862 | index_gamer_device_sightings_on_gamer_id | 4360 |
> RowExclusiveLock | t
> 19719 | gamer_device_sightings_pkey | 4360 |
> RowExclusiveLock | t
> 19309 | gamer_device_sightings | 4360 |
> ShareUpdateExclusiveLock | t
>
>
>
> The error I described seems to terminate the auto vacuum process: It has
> never finished on that table.
> It is the only table without a finished vacuum. So I guess the above error
> is the reason for this.
>
> Is there anything that I can do to get that fixed? Should I worry about
> the error? (I would not if the vacuum would run through).
>
> Any tips, any help would be much appreciated!
>
> Thank you very much! And sorry once more for my posting mistake
> Karl
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Fri, Nov 15, 2013 at 10:16 AM, Karl Hafner <karl@scoreloop.com> wrote:
>
>> Dear mailing-list,
>>
>> I am currently worried about an error that shows up in our log files
>> since a few weeks:
>>
>> 2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR: MultiXactId 2683601542
>> does no longer exist -- apparent wraparound
>> 2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT: automatic vacuum of
>> table "scoreloop.public.gamer_device_sightings"
>>
>> It seems that "autovacuum" is active on that table, but it seems to have
>> restarted today in the morning:
>>
>> select query_start, query, state, pid from pg_stat_activity where query
>> LIKE 'autovacuum%' ;
>>
>> XXX=# select query_start, query, state, pid from pg_stat_activity where
>> query LIKE 'autovacuum%' ;
>>
>> query_start | query
>> | state | pid
>>
>> -------------------------------+----------------------------------------------------------------------------------+--------+------
>> 2013-11-15 07:13:13.281202+00 | autovacuum: VACUUM ANALYZE
>> public.gamer_device_sightings (to prevent wraparound) | active | 4360
>>
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re:
2013-11-15 09:16 (no subject) Karl Hafner <karl@scoreloop.com>
@ 2013-11-22 15:18 ` Alvaro Herrera <alvherre@2ndquadrant.com>
1 sibling, 0 replies; 4+ messages in thread
From: Alvaro Herrera @ 2013-11-22 15:18 UTC (permalink / raw)
To: Karl Hafner <karl@scoreloop.com>; +Cc: pgsql-admin@postgresql.org, Strahinja Kustudić <strahinjak@nordeus.com>
Hi,
Karl Hafner wrote:
> I am currently worried about an error that shows up in our log files since
> a few weeks:
>
> 2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR: MultiXactId 2683601542 does
> no longer exist -- apparent wraparound
> 2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT: automatic vacuum of table
> "scoreloop.public.gamer_device_sightings"
So you're running 9.3.
Can you please share the output of pg_controldata and a directory
listing of pg_multixact/offsets?
> Since the autovacuum process is failing each time because of: "ERROR:
> MultiXactId 2683601542 does no longer exist -- apparent wraparound", I
> have expected the manual vacuum also to fail because of the same error.
> I've tried it anyway. Well ... manual vacuum also fails unfortunately.
Yeah, it's unlikely a manual vacuum (of either kind) would succeed.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2013-11-22 15:18 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-11-15 09:16 Karl Hafner <karl@scoreloop.com>
2013-11-15 09:33 ` Re: Karl Hafner <karl@scoreloop.com>
2013-11-16 20:25 ` Re: =?ISO-8859-2?Q?Strahinja_Kustudi=E6?= <strahinjak@nordeus.com>
2013-11-22 15:18 ` Re: Alvaro Herrera <alvherre@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox