technology16 / pgsqlblocks Goto Github PK

Просьба если есть возможность, добавить сортировку по названию БД и кол-ву процессов в окне названий БД. И если можно, возможность переставлять их (строки названий БД) в произвольном порядке, возможно если будет ещё возможность, добавить группы.

Здравствуйте,
Почему-то блокирующий запрос отобразился не полностью, впервые заметил сегодня, до этого все запросы отображались нормально, запрос COPY

I use pgSqlBlocks-1.4.0-Windows-64.jar
Sorting does not work on column STATE in postgresql 10. Оn postgresql 9.6 is working.
Sometime I get an error:
An error has occurred. See error log for more details.
java.lang.NullPointerException

Fails to start with exception:
java.lang.NullPointerException        at org.eclipse.swt.widgets.TabFolder.gtk_switch_page(Unknown Source)        at org.eclipse.swt.widgets.Widget.windowProc(Unknown Source)        at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)        at org.eclipse.swt.internal.gtk.OS._gtk_widget_show(Native Method)        at org.eclipse.swt.internal.gtk.OS.gtk_widget_show(Unknown Source)        at org.eclipse.swt.widgets.TabFolder.createItem(Unknown Source)        at org.eclipse.swt.widgets.TabItem.createWidget(Unknown Source)        at org.eclipse.swt.widgets.TabItem.<init>(Unknown Source)        at ru.taximaxim.pgsqlblocks.MainForm.createContents(MainForm.java:200)        at org.eclipse.jface.window.Window.create(Window.java:430)        at org.eclipse.jface.window.Window.open(Window.java:792)        at ru.taximaxim.pgsqlblocks.MainForm.main(MainForm.java:104)

блокировки считаются как процессы

Сортировка по столбцам в главном окне программы и в окне просмотра логов

Если включено авто обновление обновление блокировок и выделена строка, то если прокрутить таблицу далее для просмотра текущих запросов, то после обновления информации таблица прокрутится назад до выделенной строки.

Не удобно при большом количестве выполняемых запросов..

Если пароль не указан в настройках pgsqlblocks и в .pgpass, то вывести окно для ввода пароля. В целях безопасности, когда не хочется сохранять пароль.

Доброго времени суток!
Сегодня 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

Hello,

The program crashes while running with error:

in log files there is messages like:
2020-06-04T17:34:37,447 [pool-24-thread-1] ERROR ru.taximaxim.pgsqlblocks.modules.db.controller.DBController [] - ?????? ??? ????????? ????????? ??? localhost.local org.postgresql.util.PSQLException: Ran out of memory retrieving query results. at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2212) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:311) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:447) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:368) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:159) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:109) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at ru.taximaxim.pgsqlblocks.modules.db.controller.DBController.loadProcesses(DBController.java:291) ~[pgSqlBlocks-1.7.3-Linux-64.jar:1.7.3] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_212] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_212] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_212] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_212] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_212] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_212] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212] Caused by: java.lang.OutOfMemoryError: Java heap space
Exception occurred java.lang.ArrayIndexOutOfBoundsException Exception occurred java.lang.ArrayIndexOutOfBoundsException org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument not valid) at org.eclipse.swt.SWT.error(SWT.java:4720) at org.eclipse.swt.SWT.error(SWT.java:4635) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:188) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4910) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4432) at org.eclipse.jface.window.Window.runEventLoop(Window.java:823) at org.eclipse.jface.window.Window.open(Window.java:799) at ru.taximaxim.pgsqlblocks.modules.application.view.ApplicationView.show(ApplicationView.java:85) at ru.taximaxim.pgsqlblocks.modules.application.controller.ApplicationController.launch(ApplicationController.java:45) at ru.taximaxim.pgsqlblocks.PgSqlBlocks.launch(PgSqlBlocks.java:49) at ru.taximaxim.pgsqlblocks.PgSqlBlocks.main(PgSqlBlocks.java:35) Caused by: java.lang.IllegalArgumentException: Argument not valid at org.eclipse.swt.SWT.error(SWT.java:4701) at org.eclipse.swt.SWT.error(SWT.java:4635) at org.eclipse.swt.SWT.error(SWT.java:4606) at org.eclipse.swt.custom.DefaultContent.error(DefaultContent.java:682) at org.eclipse.swt.custom.DefaultContent.getOffsetAtLine(DefaultContent.java:652) at org.eclipse.swt.custom.StyledTextRenderer.textChanging(StyledTextRenderer.java:1764) at org.eclipse.swt.custom.StyledText.handleTextChanging(StyledText.java:6436) at org.eclipse.swt.custom.StyledText$5.textChanging(StyledText.java:5770) at org.eclipse.swt.custom.StyledTextListener.handleEvent(StyledTextListener.java:80) at org.eclipse.swt.custom.DefaultContent.sendTextEvent(DefaultContent.java:810) at org.eclipse.swt.custom.DefaultContent.replaceTextRange(DefaultContent.java:794) at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7433) at org.eclipse.swt.custom.StyledText.replaceTextRange(StyledText.java:8056) at org.eclipse.swt.custom.StyledText.append(StyledText.java:1534) at ru.taximaxim.pgsqlblocks.modules.logs.view.LogsView.lambda$new$1(LogsView.java:57) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) ... 8 more org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.OutOfMemoryError: Java heap space) at org.eclipse.swt.SWT.error(SWT.java:4720) at org.eclipse.swt.SWT.error(SWT.java:4635) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:188) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4910) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4432) at org.eclipse.jface.window.Window.runEventLoop(Window.java:823) at org.eclipse.jface.window.Window.open(Window.java:799) at ru.taximaxim.pgsqlblocks.modules.application.view.ApplicationView.show(ApplicationView.java:85) at ru.taximaxim.pgsqlblocks.modules.application.controller.ApplicationController.launch(ApplicationController.java:45) at ru.taximaxim.pgsqlblocks.PgSqlBlocks.launch(PgSqlBlocks.java:49) at ru.taximaxim.pgsqlblocks.PgSqlBlocks.main(PgSqlBlocks.java:35) Caused by: java.lang.OutOfMemoryError: Java heap space org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument not valid) Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

Code coverage is an important part of project maintenance.

That whould be nice:

• Settings - new param where to save blocks journals
• Blocks journal tab - button and operation to save current journal
• Saved blocks journal - button and operation so export/save as focused/marked saved blocks journals

Ошибочка в pgSqlBlocks 1.4.0

An error has occurred. See error log for more details.
Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@312aa7c rejected from java.util.concurrent.ScheduledThreadPoolExecutor@31ea9581[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 291]

При этом приложение перестало закрываться. Ошибка возникла при повторной попытке подключения к базе.

java -jar ~/Downloads/pgSqlBlocks-1.8.0-Macosx-64.jar
***WARNING: Display must be created on main thread due to Cocoa restrictions. Use vmarg -XstartOnFirstThread
2023-02-14T15:47:35,977 [main] ERROR ru.taximaxim.pgsqlblocks.modules.application.view.ApplicationView [] - An error has occurred:org.eclipse.swt.SWTException: Invalid thread access

С использованием SWT_GTK3=0 результат такой же. Пробовал разные версии.

java --version
openjdk 17.0.5 2022-10-18 LTS
OpenJDK Runtime Environment Corretto-17.0.5.8.1 (build 17.0.5+8-LTS)
OpenJDK 64-Bit Server VM Corretto-17.0.5.8.1 (build 17.0.5+8-LTS, mixed mode, sharing)