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 1uTBrq-0015A2-0K for pgsql-novice@arkaria.postgresql.org; Sun, 22 Jun 2025 03:59:42 +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 1uTBrn-00AsVx-SW for pgsql-novice@arkaria.postgresql.org; Sun, 22 Jun 2025 03:59:40 +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 1uTBrn-00AsVp-Jw for pgsql-novice@lists.postgresql.org; Sun, 22 Jun 2025 03:59:40 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uTBrm-003KOL-1U for pgsql-novice@lists.postgresql.org; Sun, 22 Jun 2025 03:59:39 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-ad93ff9f714so543111366b.2 for ; Sat, 21 Jun 2025 20:59:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750564776; x=1751169576; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=4BZ1PuUB7GLtlDi3gmow1STnxUjGiXCZng2cGmHJO5w=; b=gNS+4VG/XNWFrXmUmeAJbEyKQJZ7zXhrovziVFG5G7iSCi18vqeJ+OZYMV7X/QsnCO bTs2fMgq6XK48+rnTKc71Lk5pwDwzlEzifjbBAOnKuvlZ1mA8UVEQvRdK5dCXHmRsO2P ybL0fNPRhoL9cGwCWyUyOF8wl/G9OQG2pZtuJJO3Q0NeSV1QUZijfU6COciW8w0NtDqa lD5d4f90Hhm5yAu7iCFkM57lrdPamSjFULJx+sljh6hnW4c78VPqjhnqM576Vpn7g9Fo 8x1AX8WOm0s1FUfcpU3N6z4KP6w7YPh/O4UMGRPmczelLObLJInA8y1E0XortAZDGYK6 5bcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750564776; x=1751169576; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4BZ1PuUB7GLtlDi3gmow1STnxUjGiXCZng2cGmHJO5w=; b=tF1ZJcioN0x/kROCQM6gcc+Q7s3TNQ9/cB8m7T8NM4GUaTsXe3YK4kkNWL/sVF+rBe pplJ3ipVHlUg5iCKMf9tc/kAr33aaiz0Ne75CrE0yCkIyDz80Ek212EBt+Itx0bRQstY ZYt4T9KhkJpfuSqvmLUkblh4n8CQeBbjSJxrotq2hAhFsr7Pvfi5jwN8Ojqx/SB4fWwl 0VKnjeEEA0JVFLR7+tdIEBFSAvcKLkOEYX3qEOTcFAbw098gBPtBdzSX580/H7ZLDXF3 W5mU+RE9XpE21hbja7WsqZyxtvnXf9Sw/JSWFxF5DOweG00Qw/VGElo7HnCXKw0ET+JA 3RLg== X-Gm-Message-State: AOJu0YyFLI9KSty2HnJL/Zz4dHJZNjT3UXQ2S52RVau/u8ys4H9227Ag Vo313oeVyFn7m1Zzln4Y4HHpKfGfFvsEFxPV2FcUOCAdLE/zRpT+wCJnJaTczRhgqIaUgvFcMfu uivkqGHhXbaKz7ChsdljhjsXDUHtqu1xv6Q== X-Gm-Gg: ASbGncu6sUXFTpBKuwCsBZRZcoRSPhBKiZqHzkJtHzqQSrTTYzMvMmGrtIjiUfhaY91 fwBIct9eDGI4f4FUcRk+N5M1huw95TbiyEeE4SRtgzl3dK184Cx5bwtbRm5hqIZK8krpYNsiYhe TMs6MXWSArk5bqgFpUtBnKDnqBCF2zQjDVEHyFoJEZFi6GXNMSTMYVV7yOvcHg1jNmQ33Abi1zU 1V1 X-Google-Smtp-Source: AGHT+IGxn67lH23/Wdj49t4ly8p/15p2uIJ7jl38hJrq1soEJ5ngeVSoqSKaEnvsoEi27p2NBvqFDhLx7tog/7yVouY= X-Received: by 2002:a17:907:6088:b0:ad4:8ec1:8fc9 with SMTP id a640c23a62f3a-ae057b90470mr695468366b.42.1750564776116; Sat, 21 Jun 2025 20:59:36 -0700 (PDT) MIME-Version: 1.0 From: Sherman Willden Date: Sat, 21 Jun 2025 21:59:24 -0600 X-Gm-Features: Ac12FXyEpWAB_x0rcLYohA2fYZHF2nUC4Sy0S117HqBqKbqi-QEmsL7-UCp0q18 Message-ID: Subject: RE: Postgresql not acting like I think it should To: pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000a30a140638211fa9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a30a140638211fa9 Content-Type: text/plain; charset="UTF-8" I am the one who said that the postgresql I was using didn't act like any other one I have used before. Nothing seemed to fix it. Then I performed ls -C only to get a single column. So something really bad had happened. I reloaded Ubuntu 24.04 and now postgresql and ls are performing as advertised. I don't know what I did to my machine but it seemed totally messed up before I reloaded it. I am so glad that I have a very good files backup system. Thanks to all that replied to my first post. Sherman --000000000000a30a140638211fa9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am the one who said that the postgresql I was using= didn't act like any other one I have used before. Nothing seemed to fi= x it. Then I performed ls -C only to get a single column. So something real= ly bad had happened. I reloaded Ubuntu 24.04 and now postgresql and ls are = performing as advertised. I don't know what I did to my machine but it = seemed totally messed up before I reloaded it. I am so glad that I have a v= ery good files backup system. Thanks to all that replied to my first post.<= /div>

Sherman
--000000000000a30a140638211fa9--