| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Ninad Shah <nshah(dot)postgres(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-08-31 07:56:49 |
| Message-ID: | CAKFQuwZiG4T_X_TF+Ln-Ok6bCAf7bZac7KDEPRLzv_U3n5xzQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | basti | 2021-08-31 08:36:24 | prevent WAL replication to fill filesystem |
| Previous Message | Ninad Shah | 2021-08-31 07:46:40 | Re: Issue with a query while running on a remote host |