Thanks, patch applied.
On Thu, Feb 15, 2018 at 4:23 PM, Joao De Almeida Pereira <
> Hello Murtuza,
> Looks like I missread the Issue then.
> In that case I think it might be the solution that we can implement.
> Unless anyone in the list as a different idea.
> On Thu, Feb 15, 2018 at 11:12 AM Murtuza Zabuawala <murtuza.zabuawala@
> enterprisedb.com> wrote:
>> Hi Joao,
>> It was mainly intended for PostgreSQL database logs and not pgAdmin4 logs
>> Murtuza Zabuawala
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>> On Thu, Feb 15, 2018 at 8:03 PM, Joao De Almeida Pereira <
>> jdealmeidapere...@pivotal.io> wrote:
>>> Hello Murtuza,
>>> I was looking into the Issue information and the solution that was
>>> provided there needs some polish. With the solution that was asked, the log
>>> will still be generated, but eventually will not show up in a log monitor,
>>> but nevertheless will be there.
>>> After some digging around the code I saw that we are using Logging Level
>>> 25 for all SQL queries what if we give 24 for the dashboard logs?
>>> Another option, that I didn't look into very much was the possibility of
>>> passing a logger into the execution functions or even somehow tag them so
>>> we can have more control over the logs that we generate. It would be nice
>>> if we could somehow ignore all the logs from the Dashboard. (
>>> What do you think about the suggestion?
>>> On Thu, Feb 15, 2018 at 8:51 AM Murtuza Zabuawala <murtuza.zabuawala@
>>> enterprisedb.com> wrote:
>>>> PFA patch to add marker in dashboard queries, it will allow to user to
>>>> filter out those queries from database logs if required.
>>>> Murtuza Zabuawala
>>>> EnterpriseDB: http://www.enterprisedb.com
>>>> The Enterprise PostgreSQL Company
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company