pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
7+ messages / 4 participants
[nested] [flat]

* BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
@ 2022-06-22 20:37 PG Bug reporting form <noreply@postgresql.org>
  2022-06-22 20:46 ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
  2022-06-23 03:45 ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 2 replies; 7+ messages in thread

From: PG Bug reporting form @ 2022-06-22 20:37 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: kwolf@veritone.com

The following bug has been logged on the website:

Bug reference:      17529
Logged by:          Kevin Wolf
Email address:      kwolf@veritone.com
PostgreSQL version: 11.8
Operating system:   macbook
Description:        

When running the following command, it returns the terminating connection
error message due to administrator command

SELECT  i.indexrelid::regclass,
       s.leaf_fragmentation
FROM pg_index AS i
   JOIN pg_class AS t ON i.indexrelid = t.oid
   JOIN pg_opclass AS opc ON i.indclass[0] = opc.oid
   JOIN pg_am ON opc.opcmethod = pg_am.oid
   CROSS JOIN LATERAL pgstatindex(i.indexrelid) AS s
   where s.leaf_fragmentation > 80
   and s.leaf_fragmentation != 'NaN'::NUMERIC
   --order by 2 desc
   limit 10

Additional error info: data source was invalidated



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
  2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
@ 2022-06-22 20:46 ` Kevin Wolf <kwolf@veritone.com>
  2022-06-23 19:27   ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Jeff Janes <jeff.janes@gmail.com>
  1 sibling, 1 reply; 7+ messages in thread

From: Kevin Wolf @ 2022-06-22 20:46 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org

Additional information from the log:

!SESSION 2022-06-22 15:44:46.278
-----------------------------------------------

eclipse.buildId=unknown

java.version=11.0.12

java.vendor=Eclipse Foundation

BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US

Framework arguments:  -keyring /Users/kwolf/.eclipse_keyring

Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -keyring
/Users/kwolf/.eclipse_keyring


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 15:58:21.480

!MESSAGE Operation failed. Retry count remains = 1

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 15:58:21.481

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 15:58:21.481

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 15:58:21.481

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:03:53.594

!MESSAGE Operation failed. Retry count remains = 1

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:03:53.594

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:03:53.594

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:03:53.595

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 2 0 2022-06-22 16:05:58.767

!MESSAGE org.jkiss.dbeaver.model.exec.DBCException: Can't determine
transaction isolation - timeout

!SUBENTRY 1 org.jkiss.dbeaver.model 2 0 2022-06-22 16:05:58.767

!MESSAGE Can't determine transaction isolation - timeout

!STACK 0

org.jkiss.dbeaver.model.exec.DBCException: Can't determine transaction
isolation - timeout

at
org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.getTransactionIsolation(JDBCExecutionContext.java:293)

at
org.jkiss.dbeaver.ui.actions.datasource.DataSourceAutoCommitHandler.updateElement(DataSourceAutoCommitHandler.java:105)

at
org.eclipse.ui.internal.handlers.HandlerProxy.updateElement(HandlerProxy.java:434)

at
org.eclipse.ui.internal.handlers.E4HandlerProxy.updateElement(E4HandlerProxy.java:123)

at
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler.updateElement(WorkbenchHandlerServiceHandler.java:45)

at
org.eclipse.ui.internal.commands.CommandService$1.run(CommandService.java:261)

at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)

at
org.eclipse.ui.internal.commands.CommandService.refreshElements(CommandService.java:265)

at org.jkiss.dbeaver.ui.ActionUtils.lambda$0(ActionUtils.java:426)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)

at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4320)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3943)

at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)

at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)

at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)

at
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)

at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)

at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)

at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)

at
org.jkiss.dbeaver.ui.app.standalone.DBeaverApplication.start(DBeaverApplication.java:270)

at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)

at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)

at java.base/java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)

at org.eclipse.equinox.launcher.Main.run(Main.java:1467)


!ENTRY org.jkiss.dbeaver.model 2 0 2022-06-22 16:07:15.030

!MESSAGE org.jkiss.dbeaver.model.exec.DBCException: Can't determine
transaction isolation - timeout

!SUBENTRY 1 org.jkiss.dbeaver.model 2 0 2022-06-22 16:07:15.030

!MESSAGE Can't determine transaction isolation - timeout

!STACK 0

org.jkiss.dbeaver.model.exec.DBCException: Can't determine transaction
isolation - timeout

at
org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.getTransactionIsolation(JDBCExecutionContext.java:293)

at
org.jkiss.dbeaver.ui.actions.datasource.DataSourceAutoCommitHandler.updateElement(DataSourceAutoCommitHandler.java:105)

at
org.eclipse.ui.internal.handlers.HandlerProxy.updateElement(HandlerProxy.java:434)

at
org.eclipse.ui.internal.handlers.E4HandlerProxy.updateElement(E4HandlerProxy.java:123)

at
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler.updateElement(WorkbenchHandlerServiceHandler.java:45)

at
org.eclipse.ui.internal.commands.CommandService$1.run(CommandService.java:261)

at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)

at
org.eclipse.ui.internal.commands.CommandService.refreshElements(CommandService.java:265)

at org.jkiss.dbeaver.ui.ActionUtils.lambda$0(ActionUtils.java:426)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)

at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4320)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3943)

at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)

at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)

at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)

at
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)

at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)

at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)

at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)

at
org.jkiss.dbeaver.ui.app.standalone.DBeaverApplication.start(DBeaverApplication.java:270)

at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)

at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)

at java.base/java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)

at org.eclipse.equinox.launcher.Main.run(Main.java:1467)


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:21.352

!MESSAGE Error getting transaction isolation level

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:21.352

!MESSAGE This connection has been closed.

!STACK 0

org.postgresql.util.PSQLException: This connection has been closed.

at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:880)

at org.postgresql.jdbc.PgConnection.getAutoCommit(PgConnection.java:840)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:442)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgConnection.execSQLQuery(PgConnection.java:477)

at org.postgresql.jdbc.PgConnection.execSQLQuery(PgConnection.java:470)

at
org.postgresql.jdbc.PgConnection.getTransactionIsolation(PgConnection.java:910)

at
org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.lambda$1(JDBCExecutionContext.java:283)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.lambda$0(JDBCExecutionContext.java:281)

at
org.jkiss.dbeaver.utils.RuntimeUtils$MonitoringTask.run(RuntimeUtils.java:430)

at org.jkiss.dbeaver.utils.RuntimeUtils$1.run(RuntimeUtils.java:227)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:21.353

!MESSAGE Error getting transaction isolation level

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:21.353

!MESSAGE This connection has been closed.

!STACK 0

org.postgresql.util.PSQLException: This connection has been closed.

at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:880)

at org.postgresql.jdbc.PgConnection.getAutoCommit(PgConnection.java:840)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:442)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgConnection.execSQLQuery(PgConnection.java:477)

at org.postgresql.jdbc.PgConnection.execSQLQuery(PgConnection.java:470)

at
org.postgresql.jdbc.PgConnection.getTransactionIsolation(PgConnection.java:910)

at
org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.lambda$1(JDBCExecutionContext.java:283)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.lambda$0(JDBCExecutionContext.java:281)

at
org.jkiss.dbeaver.utils.RuntimeUtils$MonitoringTask.run(RuntimeUtils.java:430)

at org.jkiss.dbeaver.utils.RuntimeUtils$1.run(RuntimeUtils.java:227)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:23.151

!MESSAGE Operation failed. Retry count remains = 1

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:23.152

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:23.152

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:09:23.152

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:14:56.455

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command


Error position:


Error position:

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:14:56.455

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:14:56.455

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:14:56.455

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:16:00.104

!MESSAGE SQL Error [57014]: ERROR: canceling statement due to user request


Error position:

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:16:00.104

!MESSAGE SQL Error [57014]: ERROR: canceling statement due to user request

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:16:00.104

!MESSAGE ERROR: canceling statement due to user request

!STACK 0

org.postgresql.util.PSQLException: ERROR: canceling statement due to user
request

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:21:25.678

!MESSAGE Operation failed. Retry count remains = 1

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:21:25.678

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:21:25.678

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:21:25.678

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:26:57.886

!MESSAGE Operation failed. Retry count remains = 1

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:26:57.887

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:26:57.887

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:26:57.887

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:32:27.308

!MESSAGE Operation failed. Retry count remains = 1

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:32:27.308

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:32:27.308

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:32:27.308

!MESSAGE An I/O error occurred while sending to the backend.


!ENTRY org.jkiss.dbeaver.model 4 0 2022-06-22 16:37:59.747

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command


Error position:


Error position:

!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-06-22 16:37:59.747

!MESSAGE SQL Error [57P01]: FATAL: terminating connection due to
administrator command

!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-06-22 16:37:59.747

!MESSAGE FATAL: terminating connection due to administrator command

!STACK 0

org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command

at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)

at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2297)

at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)

at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:322)

at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:308)

at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:284)

at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:279)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:329)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.lambda$0(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.utils.SecurityManagerUtils.wrapDriverActions(SecurityManagerUtils.java:94)

at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:575)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)

at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)

at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)

at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)

at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)

at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-06-22 16:37:59.747

!MESSAGE An I/O error occurred while sending to the backend.




On Wed, Jun 22, 2022 at 4:38 PM PG Bug reporting form <
noreply@postgresql.org> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      17529
> Logged by:          Kevin Wolf
> Email address:      kwolf@veritone.com
> PostgreSQL version: 11.8
> Operating system:   macbook
> Description:
>
> When running the following command, it returns the terminating connection
> error message due to administrator command
>
> SELECT  i.indexrelid::regclass,
>        s.leaf_fragmentation
> FROM pg_index AS i
>    JOIN pg_class AS t ON i.indexrelid = t.oid
>    JOIN pg_opclass AS opc ON i.indclass[0] = opc.oid
>    JOIN pg_am ON opc.opcmethod = pg_am.oid
>    CROSS JOIN LATERAL pgstatindex(i.indexrelid) AS s
>    where s.leaf_fragmentation > 80
>    and s.leaf_fragmentation != 'NaN'::NUMERIC
>    --order by 2 desc
>    limit 10
>
> Additional error info: data source was invalidated
>
>

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
  2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
  2022-06-22 20:46 ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
@ 2022-06-23 19:27   ` Jeff Janes <jeff.janes@gmail.com>
  2022-06-23 19:34     ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
  0 siblings, 1 reply; 7+ messages in thread

From: Jeff Janes @ 2022-06-23 19:27 UTC (permalink / raw)
  To: Kevin Wolf <kwolf@veritone.com>; +Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>

On Wed, Jun 22, 2022 at 11:27 PM Kevin Wolf <kwolf@veritone.com> wrote:

>
> Additional information from the log:
>

That seems to be the client log.  You need to find info from the db server
log.

Cheers,

Jeff

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
  2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
  2022-06-22 20:46 ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
  2022-06-23 19:27   ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Jeff Janes <jeff.janes@gmail.com>
@ 2022-06-23 19:34     ` Kevin Wolf <kwolf@veritone.com>
  2022-06-23 19:55       ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Jeff Janes <jeff.janes@gmail.com>
  0 siblings, 1 reply; 7+ messages in thread

From: Kevin Wolf @ 2022-06-23 19:34 UTC (permalink / raw)
  To: Jeff Janes <jeff.janes@gmail.com>; +Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>

Jeff,

Where is the db server log ?  Is there a config line item for the log?
This is actually running on a docker container.


On Thu, Jun 23, 2022 at 3:27 PM Jeff Janes <jeff.janes@gmail.com> wrote:

> On Wed, Jun 22, 2022 at 11:27 PM Kevin Wolf <kwolf@veritone.com> wrote:
>
>>
>> Additional information from the log:
>>
>
> That seems to be the client log.  You need to find info from the db server
> log.
>
> Cheers,
>
> Jeff
>

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
  2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
  2022-06-22 20:46 ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
  2022-06-23 19:27   ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Jeff Janes <jeff.janes@gmail.com>
  2022-06-23 19:34     ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
@ 2022-06-23 19:55       ` Jeff Janes <jeff.janes@gmail.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Jeff Janes @ 2022-06-23 19:55 UTC (permalink / raw)
  To: Kevin Wolf <kwolf@veritone.com>; +Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>

On Thu, Jun 23, 2022 at 3:35 PM Kevin Wolf <kwolf@veritone.com> wrote:

>
> Jeff,
>
> Where is the db server log ?  Is there a config line item for the log?
> This is actually running on a docker container.
>
>
That is highly configurable.  Common defaults would be in /var/log/, or in
the 'log' subdirectory of the data folder.  I don't know what docker images
usually do.

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
  2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
@ 2022-06-23 03:45 ` David G. Johnston <david.g.johnston@gmail.com>
  2022-06-23 15:58   ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command Kevin Wolf <kwolf@veritone.com>
  1 sibling, 1 reply; 7+ messages in thread

From: David G. Johnston @ 2022-06-23 03:45 UTC (permalink / raw)
  To: kwolf@veritone.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

On Wed, Jun 22, 2022 at 8:27 PM PG Bug reporting form <
noreply@postgresql.org> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      17529
> Logged by:          Kevin Wolf
> Email address:      kwolf@veritone.com
> PostgreSQL version: 11.8
> Operating system:   macbook
> Description:
>
> When running the following command, it returns the terminating connection
> error message due to administrator command
>
> SELECT  i.indexrelid::regclass,
>        s.leaf_fragmentation
> FROM pg_index AS i
>    JOIN pg_class AS t ON i.indexrelid = t.oid
>    JOIN pg_opclass AS opc ON i.indclass[0] = opc.oid
>    JOIN pg_am ON opc.opcmethod = pg_am.oid
>    CROSS JOIN LATERAL pgstatindex(i.indexrelid) AS s
>    where s.leaf_fragmentation > 80
>    and s.leaf_fragmentation != 'NaN'::NUMERIC
>    --order by 2 desc
>    limit 10
>
>
I cannot reproduce on HEAD (in basically an empty database) and you are 2
years out of support.  Please upgrade to 11.16 and try again.

Please try to produce a somewhat more succinct test case and log output,
preferably without JDBC involved (that query can be executed in psql)
should the problem persist after updating to the current supported release.

David J.

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
  2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
  2022-06-23 03:45 ` Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command David G. Johnston <david.g.johnston@gmail.com>
@ 2022-06-23 15:58   ` Kevin Wolf <kwolf@veritone.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Kevin Wolf @ 2022-06-23 15:58 UTC (permalink / raw)
  To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

David,

Thanks for that feedback.  Just so you are aware, the command also failed
when running it in PSQL. :

postgres=# SELECT  i.indexrelid::regclass,

s.leaf_fragmentation

FROM pg_index AS i

JOIN pg_class AS t ON i.indexrelid = t.oid

JOIN pg_opclass AS opc ON i.indclass[0] = opc.oid

JOIN pg_am ON opc.opcmethod = pg_am.oid

CROSS JOIN LATERAL pgstatindex(i.indexrelid) AS s

where s.leaf_fragmentation > 80

and s.leaf_fragmentation != 'NaN'::NUMERIC

--order by 2 desc

limit 10;

Returned :

FATAL:  terminating connection due to administrator command
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
psql (14.3, server 11.8 (Debian 11.8-1.pgdg90+1))


On Wed, Jun 22, 2022 at 11:45 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:

> On Wed, Jun 22, 2022 at 8:27 PM PG Bug reporting form <
> noreply@postgresql.org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference:      17529
>> Logged by:          Kevin Wolf
>> Email address:      kwolf@veritone.com
>> PostgreSQL version: 11.8
>> Operating system:   macbook
>> Description:
>>
>> When running the following command, it returns the terminating connection
>> error message due to administrator command
>>
>> SELECT  i.indexrelid::regclass,
>>        s.leaf_fragmentation
>> FROM pg_index AS i
>>    JOIN pg_class AS t ON i.indexrelid = t.oid
>>    JOIN pg_opclass AS opc ON i.indclass[0] = opc.oid
>>    JOIN pg_am ON opc.opcmethod = pg_am.oid
>>    CROSS JOIN LATERAL pgstatindex(i.indexrelid) AS s
>>    where s.leaf_fragmentation > 80
>>    and s.leaf_fragmentation != 'NaN'::NUMERIC
>>    --order by 2 desc
>>    limit 10
>>
>>
> I cannot reproduce on HEAD (in basically an empty database) and you are 2
> years out of support.  Please upgrade to 11.16 and try again.
>
> Please try to produce a somewhat more succinct test case and log output,
> preferably without JDBC involved (that query can be executed in psql)
> should the problem persist after updating to the current supported release.
>
> David J.
>

^ permalink  raw  reply  [nested|flat] 7+ messages in thread


end of thread, other threads:[~2022-06-23 19:55 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-06-22 20:37 BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command PG Bug reporting form <noreply@postgresql.org>
2022-06-22 20:46 ` Kevin Wolf <kwolf@veritone.com>
2022-06-23 19:27   ` Jeff Janes <jeff.janes@gmail.com>
2022-06-23 19:34     ` Kevin Wolf <kwolf@veritone.com>
2022-06-23 19:55       ` Jeff Janes <jeff.janes@gmail.com>
2022-06-23 03:45 ` David G. Johnston <david.g.johnston@gmail.com>
2022-06-23 15:58   ` Kevin Wolf <kwolf@veritone.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