Hi Team,
Do we use openssl version 1.0.2, 1.1.1 or 3.0 in postgre 13.
If yes then these version are vulnerable CVE-2022-0778 which is now fixed
in later ssl version.
Regards,
Sahaj
Hi Sahaj
AFAIK this is a question for you to ask your chosen OS provider.
Postgres will be compiled against the system library (dynamic linking)
therefore whether your version of OpenSSL has been patched against the
vulnerability is a question for your OS provider, not Postgres.
Unless of cour
Hello all,
I'm experimenting with JSON-path functions, and stumbled upon this query:
SELECT jsonb_path_query('[1,2,3]', '$[*]?(@ == 4)')
It returns 0 rows. I expected it to return one row with `null` value. Isn't
it the case that `SELECT ` should always return 1 row?
Viliam
Viliam Ďurina schrieb am 23.03.2022 um 17:56:
Hello all,
I'm experimenting with JSON-path functions, and stumbled upon this query:
SELECT jsonb_path_query('[1,2,3]', '$[*]?(@ == 4)')
It returns 0 rows. I expected it to return one row with `null` value.
Isn't it the case that `SELECT ` shoul
I've just realized that. I used it as an equivalent of the standard
`JSON_QUERY` that returns a JSON value. If the expression matches multiple
values, it can wrap them in a JSON array.
Now I'm surprised that a set-returning function is even allowed in SELECT
clause where the values have to be scal
On Wed, Mar 23, 2022 at 10:10 AM Viliam Ďurina
wrote:
> Now I'm surprised that a set-returning function is even allowed in SELECT
> clause where the values have to be scalar.
>
AFAIK the lateral construct, which is required to avoid doing just this, is
a relatively recent invention for SQL. I i
"David G. Johnston" writes:
> On Wed, Mar 23, 2022 at 10:10 AM Viliam Ďurina
> wrote:
>> Now I'm surprised that a set-returning function is even allowed in SELECT
>> clause where the values have to be scalar.
> AFAIK the lateral construct, which is required to avoid doing just this, is
> a relat
