Re: Issue with a query while running on a remote host

From: Ninad Shah <nshah(dot)postgres(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Issue with a query while running on a remote host
Date: 2021-09-02 13:28:03
Message-ID: CAOFEiBfa4i-Ejs1q5gqW9WjrNk_9YY1rq-Yh_7+nm2AYSHjt5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi David/Karsten,

Thank you for your response. This helped me.

This thread can be closed.

Regards,
Ninad Shah

On Tue, 31 Aug 2021 at 13:26, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Tuesday, August 31, 2021, Ninad Shah <nshah(dot)postgres(at)gmail(dot)com> wrote:
>
>> Hi Karsten,
>>
>> I apologize for the delayed response.
>>
>> There is no script-related transfer happening here. It creates an issue
>> while using "bash@" inside a column.
>>
>>>
>>>
> That wasn’t what was meant. Ignore the “why” for the moment, the theory
> is something in the network or OS sees that string of data and fires off a
> rule that causes the data to be filtered. Period. The comment about “bash
> script” was just saying that whatever the “something” is might be guessing
> that the text sequence “bash(at)“ has something to do with bash scripts. It
> was just a hint. But regardless of why the false positive exists the
> theory is that there is one happening in the environment externally to any
> PostgreSQL related software.
>
> David J.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2021-09-02 13:55:45 Re: jsonpath duplication result
Previous Message Ninad Shah 2021-09-02 13:24:03 Re: oldest WAL files not removed