public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected]
To: [email protected]
Subject: complain about closing bugreports with wrong reason
Date: Mon, 26 Aug 2024 17:57:26 +0300
Message-ID: <[email protected]> (raw)

Hi all.
There is a bug in PgAdmin, if I use an option "set role" in the 
connection dialog, I will not be able to cancel query anymore.

How to recreate. Config connection to a server to use "set role": the 
dialog "properties" of a server, tab "connection", field "Role" assign 
to DBO, without superuser privilege.
Run query, for instance "select pg_sleep(10000)" and try to finish it.

You will get
ERROR:  permission denied to cancel query
DETAIL:  Only roles with privileges of the role whose query is being 
canceled or with privileges of the "pg_signal_backend" role may cancel 
this query.
STATEMENT:  SELECT pg_cancel_backend(497843);

First bug in the issue tracker is:
https://github.com/pgadmin-org/pgadmin4/issues/7442

The answer to assign user to the role pg_signal_backend is wrong and 
will rise even security issue, the user will be able to terminate not 
only his query, but everyone.

I reopened this bugreport for this reason.
https://github.com/pgadmin-org/pgadmin4/issues/7821

The answer was just lie:

The connection made using the details from server dialog is used 
everywhere. pgAdmin cannot create a connection separately without the 
role specified and execute pg_cancel_backend.
This is not a bug.
This behaviour is same as psql.
End cite.

The lie because a psql and DBeaver worked perfectly in this situation. 
Everyone can set role in DBeaver connection dialog or in the psql "set 
role dbo" after connection, run query and cancel query. This doesn't 
work only in the PgAdmin and only due to reason, because developers 
simply close bugs instead on fixing it.

If your way do nothing with buggy behavior of "set role", then just 
remove it from the connection dialog.
-- 
Olleg

view thread (2+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: complain about closing bugreports with wrong reason
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox