Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command

Поиск
Список
Период
Сортировка
От Kevin Wolf
Тема Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
Дата
Msg-id CAKjf5N-cRCmiykxthKDegE7Urm=Y-YDsASUZFhLHtqbQfkwn3Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-bugs

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.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Andrey Borodin
Дата:
Сообщение: Re: BUG #17528: ERROR: could not access status of transaction 1997627701
Следующее
От: Alan Lin
Дата:
Сообщение: dropdb utility command prompts for password despite valid .pgpass file in home directory