BUG #15210: Internal Server Error When Attempting to Look at Trigger Functions
The following bug has been logged on the website:
Bug reference: 15210
Logged by: Diana Petty
Email address: diana.petty@csra.com
PostgreSQL version: 10.4
Operating system: Server=Redhat, pgAdmin = Mac OS High Sierra
Description:
I log into pgAdmin pointing at either our 10.4 server or our 9.5 server - I
get the same error in both cases. I open the schema, click on trigger
functions, and click on one to show in the sql panel. Then I get the
internal server error. It doesn't matter which schema or which trigger
function. Other objects display appropriately. Here is the contents of the
log:
2018-05-25 14:07:32,657: ERROR werkzeug: Error on request:
Traceback (most recent call last):
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/werkzeug/serving.py",
line 270, in run_wsgi
execute(self.server.app)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/werkzeug/serving.py",
line 258, in execute
application_iter = app(environ, start_response)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1997, in __call__
return self.wsgi_app(environ, start_response)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1985, in wsgi_app
response = self.handle_exception(e)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1540, in handle_exception
reraise(exc_type, exc_value, tb)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1982, in wsgi_app
response = self.full_dispatch_request()
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1614, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1517, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1612, in full_dispatch_request
rv = self.dispatch_request()
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/app.py", line
1598, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/Applications/pgAdmin
4.app/Contents/Resources/venv/lib/python/site-packages/flask/views.py", line
84, in view
return self.dispatch_request(*args, **kwargs)
File "/Applications/pgAdmin
4.app/Contents/Resources/web/pgadmin/browser/utils.py", line 254, in
dispatch_request
return method(*args, **kwargs)
File "/Applications/pgAdmin
4.app/Contents/Resources/web/pgadmin/browser/server_groups/servers/databases/schemas/functions/__init__.py",
line 345, in wrap
return f(*args, **kwargs)
File "/Applications/pgAdmin
4.app/Contents/Resources/web/pgadmin/browser/server_groups/servers/databases/schemas/functions/__init__.py",
line 1053, in sql
) + '(' + res['rows'][0]['func_args'] + ')'
KeyError: 'nspname'
On Fri, May 25, 2018 at 11:23 AM, PG Bug reporting form <
noreply@postgresql.org> wrote:
The following bug has been logged on the website:
Bug reference: 15210
Logged by: Diana Petty
Email address: diana.petty@csra.com
PostgreSQL version: 10.4
Operating system: Server=Redhat, pgAdmin = Mac OS High Sierra
Description:I log into pgAdmin pointing at either our 10.4 server or our 9.5 server - I
get the same error in both cases. I open the schema, click on trigger
functions, and click on one to show in the sql panel. Then I get the
internal server error. It doesn't matter which schema or which trigger
function. Other objects display appropriately. Here is the contents of the
log:
This bug report list does not cover the external pgAdmin application.
Please see the following for guidance on reporting problems to them.
https://www.pgadmin.org/support/list/
David J.
"David G. Johnston" <david.g.johnston@gmail.com> writes:
On Fri, May 25, 2018 at 11:23 AM, PG Bug reporting form <
noreply@postgresql.org> wrote:I log into pgAdmin pointing at either our 10.4 server or our 9.5 server - I
get the same error in both cases. I open the schema, click on trigger
functions, and click on one to show in the sql panel. Then I get the
internal server error. It doesn't matter which schema or which trigger
function. Other objects display appropriately. Here is the contents of the
log:
This bug report list does not cover the external pgAdmin application.
Please see the following for guidance on reporting problems to them.
https://www.pgadmin.org/support/list/
The reference to an "internal server error" suggests that it could be
our turf, but a traceback on the client side proves nothing about that.
It might be useful to look at the server log and see if it reports any
interesting error when you do this.
regards, tom lane
I checked the server log and saw nothing that looked like it would be related to my error. But to be sure I made the error happen again and the log wasn't changed.
________________________________________
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Friday, May 25, 2018 2:39 PM
To: David G. Johnston
Cc: Petty, Diana; pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15210: Internal Server Error When Attempting to Look at Trigger Functions
"David G. Johnston" <david.g.johnston@gmail.com> writes:
On Fri, May 25, 2018 at 11:23 AM, PG Bug reporting form <
noreply@postgresql.org> wrote:I log into pgAdmin pointing at either our 10.4 server or our 9.5 server - I
get the same error in both cases. I open the schema, click on trigger
functions, and click on one to show in the sql panel. Then I get the
internal server error. It doesn't matter which schema or which trigger
function. Other objects display appropriately. Here is the contents of the
log:
This bug report list does not cover the external pgAdmin application.
Please see the following for guidance on reporting problems to them.
https://www.pgadmin.org/support/list/
The reference to an "internal server error" suggests that it could be
our turf, but a traceback on the client side proves nothing about that.
It might be useful to look at the server log and see if it reports any
interesting error when you do this.
regards, tom lane
This electronic message transmission contains information from CSRA that may be attorney-client privileged, proprietary or confidential. The information in this message is intended only for use by the individual(s) to whom it is addressed. If you believe you have received this message in error, please contact me immediately and be aware that any use, disclosure, copying or distribution of the contents of this message is strictly prohibited. NOTE: Regardless of content, this email shall not operate to bind CSRA to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of email for such purpose.
"Petty, Diana" <Diana.Petty@csra.com> writes:
I checked the server log and saw nothing that looked like it would be related to my error. But to be sure I made the error happen again and the log wasn't changed.
Hm. "Internal server error" seems to be stretching the truth then.
Anyway, at this point I'd concur with David's advice to report it to
the pgadmin list.
regards, tom lane