Re: BUG #15210: Internal Server Error When Attempting to Look at Trigger Functions

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(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Friday, May 25, 2018 2:39 PM
To: David G. Johnston
Cc: Petty, Diana; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15210: Internal Server Error When Attempting to Look at Trigger Functions

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, May 25, 2018 at 11:23 AM, PG Bug reporting form <
> noreply(at)postgresql(dot)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.