Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rmuOf-00AZCA-Rq for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2024 11:46:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rmuOe-004W1e-DT for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2024 11:46:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rmuOe-004W1W-4D for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2024 11:46:16 +0000 Received: from mail-ua1-x933.google.com ([2607:f8b0:4864:20::933]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rmuOc-005XQU-0g for pgsql-hackers@postgresql.org; Wed, 20 Mar 2024 11:46:15 +0000 Received: by mail-ua1-x933.google.com with SMTP id a1e0cc1a2514c-7e05d6871ddso1183594241.1 for ; Wed, 20 Mar 2024 04:46:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710935171; x=1711539971; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Iqjv/b1uF38Q2LZ4W5MQ0C4ITAsRRF/bUKAnicKB7eM=; b=d2OHEW4BmGAskGzqhFdt74z8JXcbBO4PHiRJjre6DCJ86AGSPbxcIKFixwqkuACVRl BcVzz5kvSxn9py4gRadf2Qc8QlRa1ZKoi8Wm5dmq8zkPbtcx6+mN8AEv3oX322rc0YYI YzVDg64u9pdKGJDMuSZy3ApgeQhKe19sIt/lmh0XuQratwcpFM0g5GbNeHCbqaS8VtKg tDXNg65IrZiYV9TykR5HgrxsgPS8hGEREAd8nLf8GvFUMzO/s272D3QF7/GTqMksW0cs xgovWh/VZ9mmfaLyvR4KUyUQVRg/QLacsmzFdjuXpUxDD4JIskZFt5Qnm7ZafcpVMOsk nGqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710935171; x=1711539971; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Iqjv/b1uF38Q2LZ4W5MQ0C4ITAsRRF/bUKAnicKB7eM=; b=k4Ut2AEwYIMuekEEqEW1Wj0WzxPjYiTckpge6xC/TzAuAyXBb33GAf897S9CSkzrDH xLE6+YCY2gOzzWvXR/gN7RgRCdtcHG6WRmxb2l6ui7b7pOc/x8fJXcOGCF7EmRgmjQPH GeLVz8NWlKUk5HIXsb/SzXXrPaThTTwTvBQCZZb3wE0iD4cggAlKQqpQ0xL6OnHgUtEz kgpjdE/3oq+mL+7u9mDuYTPl/YXOkFtsx/XFSPpdcikAHT8d9LPIWZLirYfVSVEo4bzm Ouz9GdaIekFmDuqNSjdCsinSLMBxni7oSqgppmNaeAS1raC7Tl5v58WMy5w52+J317dW eceg== X-Forwarded-Encrypted: i=1; AJvYcCWwByAraV5ir91El68siP9v+Dyn3UviCDexcnlxerlKGZcs/to4n78OGtCsoeCEc1zBfc3PqKgWi+Gowad6mpDV0NcyiC5fM9Ai2MfE X-Gm-Message-State: AOJu0YytwesoQYh7I4K0W+q9ok7LfdHM58TpBMX7IDDh8DBwwrcLXLzq tAGxpKRWI8T04Ahyfk/BVkt8I9JR/giPad75hIbfw9lWfFMHoTneZ2O/QJwSy7+XfaeTT/xxvwG MvZK62tISpvTxCbZLoVp3T3sDSUk= X-Google-Smtp-Source: AGHT+IFK4VrXNAI9gTMEbXPScWLAPWqjUGQDplIbozWHiYyFvFcbH8+hDzrw0mtIxcSwu9ogY9HUyGqFxBzruCS2Ni8= X-Received: by 2002:a67:e359:0:b0:476:6bd0:2371 with SMTP id s25-20020a67e359000000b004766bd02371mr11382039vsm.13.1710935171317; Wed, 20 Mar 2024 04:46:11 -0700 (PDT) MIME-Version: 1.0 References: <1cee81f3-312f-30e3-0282-c4df7ee72f93@xs4all.nl> <202403041503.5momp6knupgo@alvherre.pgsql> <562e5ad9-1357-4752-ad28-7e56740f74f8@enterprisedb.com> In-Reply-To: From: jian he Date: Wed, 20 Mar 2024 19:46:00 +0800 Message-ID: Subject: Re: remaining sql/json patches To: Amit Langote Cc: Tomas Vondra , Himanshu Upadhyaya , Alvaro Herrera , Erik Rijkers , Andres Freund , Andrew Dunstan , PostgreSQL-development Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk looking at documentation again. one very minor question (issue) + + The ON EMPTY clause specifies the behavior if the + path_expression yields no value at all; the + default when ON EMPTY is not specified is to return + a null value. + I think it should be: applying path_expression or evaluating path_expression not "the path_expression" ?