I have json data which is based on arbitrary levels of hierarchy. The json
objects I need to query are at an unknown depth in the document, which
means I have to use the recursive wildcard member accessor (.**)
The problem is, the path to these unknown depths also contain arrays, and
when .** acce
As always, the solution is in the postgresql documentation. Using exists()
from a filter prior to accessing an optional field solves my problem. I can
have both strict mode and access to optional fields without getting an
error this way.
On Fri, Oct 15, 2021 at 6:50 PM Seref Arikan wrote:
>
Sorry, this was meant to go to the whole group:
Very interesting!. Great work. Can you clarify how exactly you're running
postgres in your tests? A specific AWS service? What's the test
infrastructure that sits above the file system?
On Thu, Jul 17, 2025 at 11:59 PM Pierre Barre wrote:
> Hi eve
red accordingly memory-wise as well as with
> synchronous_commit = off, wal_init_zero = off and wal_recycle = off.
>
> Best,
> Pierre
>
> On Fri, Jul 18, 2025, at 12:42, Seref Arikan wrote:
>
> Sorry, this was meant to go to the whole group:
>
> Very interesting!. Great work. Can yo
