#1071 Error trying to view data in a PostgreSQL table


I use the last snapshot "20130120_1126"

The problem is this:
1) I connect to a Postgresql database and I select a table in the object tree.
2) I click on the "Content" tab to view the data in the table
3) no data is displayed, but the following error occurs:

org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283)
at net.sourceforge.squirrel_sql.client.session.mainpanel.objecttree.tabs.table.ContentsTab.createDataSet(ContentsTab.java:325)
at net.sourceforge.squirrel_sql.client.session.mainpanel.objecttree.tabs.BaseDataSetTab$1.run(BaseDataSetTab.java:128)
at net.sourceforge.squirrel_sql.fw.util.TaskExecuter.run(TaskExecuter.java:82)
at java.lang.Thread.run(Unknown Source)


  • Nick

    Nick - 2013-02-13

    Even with the last snapshot this issue is still present.

  • Gerd Wagner

    Gerd Wagner - 2013-02-13

    I think I saw such exceptions with PostgreSQL when I was working with Auto Commit off and an exception occurred. Within the open transaction any further access to the connection would then result in your exception.

    Could you please try out the following:
    - Please have a look at New Session Properties --> tab SQL and make sure Auto Commit is switched on.
    - If then the problem doesn't occur anymore please have a look at the logs and see if you can find an initial exception that caused the problem.

  • Nick

    Nick - 2013-02-14


    I have tried your suggestion and I can confirm you that with the option "Auto Commit" turned on, the problem is not present anymore.

    However I think that here there is still a problem, because with PostgreSQL I'm forced to use "auto commit" instead of manually commit when I need.

    I'm not sure what I have to do with your request here:

    • If then the problem doesn't occur anymore please have a look at the logs and see if you can find an initial exception that caused the problem.

    I have to send you the "Dump Application"? Or something else?

    Thank you for your support


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks