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 1qWZB0-003fIW-ML for pgadmin-hackers@arkaria.postgresql.org; Thu, 17 Aug 2023 09:20:23 +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 1qWZAx-00FaCa-96 for pgadmin-hackers@arkaria.postgresql.org; Thu, 17 Aug 2023 09:20:19 +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 1qWZAw-00FaCS-W8 for pgadmin-hackers@lists.postgresql.org; Thu, 17 Aug 2023 09:20:19 +0000 Received: from mail-pj1-x1036.google.com ([2607:f8b0:4864:20::1036]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qWZAt-000dlB-Hj for pgadmin-hackers@postgresql.org; Thu, 17 Aug 2023 09:20:18 +0000 Received: by mail-pj1-x1036.google.com with SMTP id 98e67ed59e1d1-2681223aaacso516558a91.0 for ; Thu, 17 Aug 2023 02:20:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692264013; x=1692868813; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ORomT2hXIa9FwaS6agLGISY3WEB0LW56EXLJjG5DGP4=; b=N/koMV/70HLbNOIxeHp0hsTfyjfIhTKO2TQZj+YPqq+on/a2O8X5eM6DPfDuHDqj0+ 2p5oXE1hm0zrO7GCn+x6NHzA8e/Oy2+78RzyhGgLlAiUbB6BK1BMI0HMh57FOXPg6bIg l4w/ujG4d4+8N5lQBrqzK3fNo5J3ynZWqKwfnQWzDnh4WaXNqqb5y9T4eB9o6nxWukKL f31Z94tkCKDp0iBbh+5ppjqPTCa/KCKk15/W9y3oHZKY2xVOVRIkqRerEo1Df+1vrhc6 eXnKt6eu/U5XJBCg9T0kyHhiE/fVit4310BE8H+B85rbt0pdJH1OTQym4DY/N3P4Npf6 sY8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692264013; x=1692868813; 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=ORomT2hXIa9FwaS6agLGISY3WEB0LW56EXLJjG5DGP4=; b=A+BiEzPQSxI+BD/kx4usO7sg7MX0eG0JrCukygfDsE1tySMy8Y4B3QRNOW8lzGSa02 4NCd8X/onlnHzbuv/b07cUue2YR3ivzC3ZTrEuCwjacquxAFsZXn8e6GODSmlDPEjq8x F37yweEvD6Tf3suYyM5qu1wZpBIgGE2+KEqkiEIAIfdLF7PheEd2jXY/K/g0gI/p7iQL +y3gIP8HOwIGS929relLvfIfbF9YiRpTWXxB9E9P6Y1FtgoatqggEOPjdXcBrd9x15F3 4zsSj0AOFnVKW/ys0qxgnSZlpPpXDcEyDzzgNfVqRIHY7str8N2NPheoPdzPf9eyLg0c aq/g== X-Gm-Message-State: AOJu0Yxld/D9LkzYArmfRhM0UQueLoTxTDMmrqAoxMatw26H0mtN26+M YCYX4E8hg+evdZfVbI3mtlWiKIBt01GYU2aO9eDxZLrOSULlTQ== X-Google-Smtp-Source: AGHT+IExxI5DuuYAFuTvmioG9iu0rZDZDSS9rHPczk4lFUqxJbkDw7UXFZq55TTruUjXY81YSMgpusv6WCKERaMt46o= X-Received: by 2002:a17:90b:4a10:b0:25d:d224:9fb9 with SMTP id kk16-20020a17090b4a1000b0025dd2249fb9mr2411471pjb.24.1692264013157; Thu, 17 Aug 2023 02:20:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Thu, 17 Aug 2023 14:50:00 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Khushboo Vashi Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="0000000000005ed8e806031aeb99" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005ed8e806031aeb99 Content-Type: text/plain; charset="UTF-8" On Thu, 17 Aug 2023 at 14:39, Khushboo Vashi < khushboo.vashi@enterprisedb.com> wrote: > Sample data of my system to fix this issue: > > 1. process331: > 1. memory_bytes:null > 2. memory_usage:null > 3. name:"QuickLookUIServi" > 4. pid:938 > 5. row_number:331 > > Okay, so it is an issue of null value then. Are null values being returned for all processes or only for specific ones? Also can you please verify it by running "SELECT * FROM pg_sys_cpu_memory_by_process();" query in the query tool? Just want to ensure I'm not making mistakes while processing the queries output. > --0000000000005ed8e806031aeb99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=3D""
On Thu, 17 Aug 2023 at 14:39, Khushboo = Vashi <khushboo.vashi= @enterprisedb.com> wrote:
Sample data o= f my system to fix this issue:
  1. process331:
    1. memory_bytes:null=
    2. memor= y_usage:null
    3. name:&quo= t;QuickLookUIServi"
    4. pid:938
    5. row_number:331
<= div>Okay, so it is an issue of null value then.
Are null values being re= turned for all processes or only for specific ones?
Also can you please= verify it by running "SELECT * FROM pg_sys_cpu_memory_by_process();&q= uot; query in the query tool? Just want to ensure I'm not making mistak= es while processing the queries output.
--0000000000005ed8e806031aeb99--