Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pgSqlBlocks 1.7.5 ERROR: out of shared memory #56

Open
makeconfig2017 opened this issue May 3, 2021 · 0 comments
Open

pgSqlBlocks 1.7.5 ERROR: out of shared memory #56

makeconfig2017 opened this issue May 3, 2021 · 0 comments

Comments

@makeconfig2017
Copy link

Доброго времени суток!
Сегодня pgSqlBlocks 1.7.5 завалил БД с ошибкой:

2021-05-03 13:54:24.844 EEST [107289] [pgSqlBlocks 1.7.5] [pgadmin] [postgres] [1.1.1.1]ERROR: out of shared memory
2021-05-03 13:54:24.844 EEST [107289] [pgSqlBlocks 1.7.5] [pgadmin] [postgres] [1.1.1.1]]HINT: You might need to increase max_locks_per_transaction.
2021-05-03 13:54:24.844 EEST [107289] [pgSqlBlocks 1.7.5] [pgadmin] [postgres] [1.1.1.1]]STATEMENT: WITH blocks AS ( SELECT blocking_locks.pid as pid, blocked_locks.p id as blocked_pid, blocking_locks.locktype as locktype, blocking_locks.relation::regclass as relation, blocking_locks.granted as granted FROM pg_catalog.pg_l ocks blocked_locks JOIN pg_catalog.pg_locks blocking_locks ON blocking_locks.locktype = blocked_locks.locktype AND blocking_locks.DATABASE IS NOT DISTINCT FROM blocked_locks.DATABASE AND blocking_locks.relation IS NOT DISTINCT FROM blocked_locks.relation AND blocking_locks.page IS NOT DISTINCT FROM blocked_locks.page AND bloc king_locks.tuple IS NOT DISTINCT FROM blocked_locks.tuple AND blocking_locks.virtualxid IS NOT DISTINCT FROM blocked_locks.virtualxid AND blocking_locks.transactionid IS NOT D ISTINCT FROM blocked_locks.transactionid AND blocking_locks.classid IS NOT DISTINCT FROM blocked_locks.classid AND blocking_locks.objid IS NOT DISTINCT FROM blocked_locks.obji d AND blocking_locks.objsubid IS NOT DISTINCT FROM blocked_locks.objsubid AND blocking_locks.pid != blocked_locks.pid WHERE NOT blocked_locks.granted)SELECT procs.pid A S pid, application_name, datname, usename, backend_type, CASE WHEN client_port=-1 THEN 'local pipe' WHEN length(client_hostname)>0 THEN client_hostname||':'||clie nt_port ELSE textin(inet_out(client_addr))||':'||client_port END AS client, date_trunc('second', backend_start) AS backend_start, CASE WHEN state='active' THEN date_tru nc('second', query_start)::text ELSE '' END AS query_start, date_trunc('second', xact_start) AS xact_start, state, date_trunc('second', state_change) AS state_chang e, blocks.pid AS blockedby, /* deprecated null::text AS blocking_locks,*/ blocks.locktype AS locktype, blocks.relation AS relation, blocks.granted AS granted, query AS query, CASE WHEN query_start IS NULL OR state<>'active' THEN false ELSE query_start < now() - '10 seconds'::interval END AS slowquery FROM pg_stat_activity procs LEFT JOIN blocks ON blocks.blocked_pid = procs.pid ORDER BY pid
2021-05-03 13:54:25.192 EEST [18617] [] [] [] []LOG: startup process (PID 18619) exited with exit code 1
2021-05-03 13:54:25.192 EEST [18617] [] [] [] []LOG: terminating any other active server processes
2021-05-03 13:54:27.116 EEST [18617] [] [] [] []LOG: database system is shut down

Впервые с таким столкнулся, PostgreSQL 10.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant