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 1szM9R-005dMT-1Z for pgsql-admin@arkaria.postgresql.org; Fri, 11 Oct 2024 20:22:17 +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 1szM9P-00ApTp-CF for pgsql-admin@arkaria.postgresql.org; Fri, 11 Oct 2024 20:22:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szM9O-00ApTh-Vc for pgsql-admin@lists.postgresql.org; Fri, 11 Oct 2024 20:22:15 +0000 Received: from mail-pl1-x631.google.com ([2607:f8b0:4864:20::631]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1szM9M-000Pqe-OL for pgsql-admin@postgresql.org; Fri, 11 Oct 2024 20:22:14 +0000 Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-20ca1b6a80aso9408405ad.2 for ; Fri, 11 Oct 2024 13:22:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728678132; x=1729282932; 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=LhnVU+Cgp7wmWh42GMaCASSK9G5fzK8eK/9EFj5/ojc=; b=C7ehWeHEJJ6o2Zrcv7lpmZXKZEMFvKGbuTKSaGTR+5WUmyi2XdSA3MHfmW9JFhKL+5 EvXQplnz42DUhui4nKV7gPK8JdDWLxVzzK3EOSfJUr3QRZNns5XjlrQ/tHHMX7RnvP3p GDR9btiA5eVxeEujn04JRoKrTYbHkUlDDS1uAR3g6/BjDSkypL3A2mNjBbsi0r5y/zcl kgxI/E4El4RHdU879AK32ek56zel1vjShMPQsq4IFyIs6IcFvk8JQ3bt24MVaxJiaSTj nuC1nSvOUCcR4sqO5c8GyFs1VNWitG7eGxD+dlVRnevpicSdIAKRXDrcfMYQo21iOFEd PT0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728678132; x=1729282932; 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=LhnVU+Cgp7wmWh42GMaCASSK9G5fzK8eK/9EFj5/ojc=; b=lyThtShifrTtcKOi+qX7ceI4AwnKr+TnPCE4A7+B0xL2LzjnGT+k2HcMUfHGMFPWmp +cuqlE8dhI/qiadOL1X8cNorWEY3/XPEgKxstS/78tjr3ykk8EoX3961VUPVMrsZwH8f ku9mmjKegtShqQgb9MrrNnzaiREfdMzvkRnXiBn8yf5HMblvr1Jen3bvaN8wLppHLHU0 0i6gj/5f4WErr+mjmar6JlAoOZBK6C5WDIBce41ZeMKpoTP73RQNjZBInSdWYIRYtWoG IH1+zqVTtmdZEJ3c8s9avMpU/EFSiOz+85IN4x8YCdEQN35Y62bDT9WTJtqWro1eUnIv Yl4Q== X-Gm-Message-State: AOJu0Yx0yS2DrpqDmyRGpzc7Tr/txHsVeY5HBgugEVAVarpQTWns0fmf OPF3deoLI2VYRNALO25JO3X80MpJ1i8uKb3VRWu86iU0klVxCHYnY+NdCpwsoNLDou1atIBbprw ECLx5lUiArlz0O+OtVI8y0+pNSqs= X-Google-Smtp-Source: AGHT+IHuPsKu53gmUqWW7Jt/WVOWlYRBnaE0VHPLHzO8aCc0jgNcQqggvu7C9URcTrwpxjHnwdhNQp0HO1pGC96l8vQ= X-Received: by 2002:a17:902:f552:b0:20c:8c51:f9f with SMTP id d9443c01a7336-20cbb24087emr14181745ad.44.1728678131602; Fri, 11 Oct 2024 13:22:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Imran Khan Date: Fri, 11 Oct 2024 23:21:57 +0300 Message-ID: Subject: Re: Unknown temp directories and library files To: Priancka Chatz Cc: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000f7213a0624393dc5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f7213a0624393dc5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Try to first restrict the access of localhost and assign a password for postgres which is known to you. Then ask Linux team or server team to share logs of logins and history of root. Finally, restart the instance to clear pgsql_tmp dir. Thanks, Imran On Fri, Oct 11, 2024, 1:20=E2=80=AFPM Priancka Chatz wro= te: > Hi admins, > > I am observing a new/unknown behavior on some of my instances. My postgre= s > Data directory path is /home/postgres/pgdata/pgroot/data. And I see a tem= p > directory present inside /home/postgres/pgdata which has 100s of director= y > underneath it and inside each directory some library files related to > Psycopg2. Not sure what these files are and why it is getting created. I = am > attaching screenshots for reference. > Can anyone shed some light or direct me to any links to troubleshoot this= ? > > Regards, > Priyanka > --000000000000f7213a0624393dc5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

=C2=A0Tr= y to first restrict the access of localhost and assign a password for postg= res which is known to you. Then ask Linux team or server team to share logs= of logins and history of root. Finally, restart the instance to clear pgsq= l_tmp dir.=C2=A0

Thanks,=
Imran

On Fri, Oct 11, 2024, 1:20=E2=80=AFPM Pr= iancka Chatz <pc9926@gmail.com&g= t; wrote:
Hi admin= s,

I am observing a new/unknown behavior on some of my i= nstances. My postgres Data directory path is /home/postgres/pgdata/pgroot/d= ata. And I see a temp directory present inside /home/postgres/pgdata which = has 100s of directory underneath it and inside each directory some library = files related to Psycopg2. Not sure what these files are and why it is gett= ing created. I am attaching screenshots for reference.
Can anyone= shed some light or direct me to any links to troubleshoot this?
=
Regards,
Priyanka
--000000000000f7213a0624393dc5--