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 1tBya6-007pvo-44 for pgsql-general@arkaria.postgresql.org; Fri, 15 Nov 2024 15:49:57 +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 1tBya3-00Aaba-1x for pgsql-general@arkaria.postgresql.org; Fri, 15 Nov 2024 15:49:55 +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 1tBya2-00AabS-Ne for pgsql-general@lists.postgresql.org; Fri, 15 Nov 2024 15:49:55 +0000 Received: from mail-lf1-x136.google.com ([2a00:1450:4864:20::136]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tBya0-0022nT-JE for pgsql-general@lists.postgresql.org; Fri, 15 Nov 2024 15:49:54 +0000 Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-539f6e1f756so1983887e87.0 for ; Fri, 15 Nov 2024 07:49:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731685790; x=1732290590; darn=lists.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=LoAb0M9noeHAyRknVc38PWEW8XFF78Q0y0pp5xsh54E=; b=WErl+usdJb3SNfRPxHdNycb1wO3gC6zFn4uDBzWmVN0TzUY3+RRaSHGornGKE8t6rR qZgoLwwHx0AWQEHWZ5B7Y1v+SpDxeDWmYzCwnhJiyY9+C4/OPvWKKspJnhMp4871laIu leymW5tXaCkFDz6ja2CZwUfT6+DM9GR6BqXncVteFyD3ZTjcZjGM/Kc4i9qfDVaocXxp WdqUrlg7sxb+IccXvQe7y5bT9oS4em+c067vlTdDDADttFbUjGB6wPOmPTefOvu6ltin /RauQ/dmoi9dUlap/g+3322teVSpFz8sq+Am7ZblzdtW1yditpSWxf7Cs+azof3PXfnI mcSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731685790; x=1732290590; 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=LoAb0M9noeHAyRknVc38PWEW8XFF78Q0y0pp5xsh54E=; b=gw7HvI/rRawdnAsoYSfSBw72IJoJAWIkgGJ6yjCzzfRFdvZGpxWg+Wp9gk8rLsLUdt qHTFSCBOoSLgoCs4rKxvCEbRbxVvPDjqm/VQsbhSNwjZE1AWP+I9DPfbkEOUcIQWr4E4 Uj3Ce4QzFiIPWKr8kkHtCx5UZvZhn54BffbzuznedRQdb6E+d26jMJEXIV/3ez299Dy1 MKFJIJTXYdT2/Uq96lM9CMAVMQPebBo21u5EJmSwNA9llQLQwSPpvD963b6Z0okVzCDx Sj2EOVsUAP2iVts45+bxfYP5lEo69NITwrRgGyneQfK87v4rF4J9ZendoULl9JWL6YBX TIkg== X-Gm-Message-State: AOJu0YyXmNpXAX7V/5sAEPXiigWeBlSW7GwIOvda5QcArbky1DsIYiMO 2mhLNqexufUUskTr9/P3QEgII2xBr9I45zYjCRVU0gnr4Uf4yHtynA+1kLg3+WOU8bTjLNIGqRr ubi8lei/RZNxq02kIJtzj9eNJyQ== X-Google-Smtp-Source: AGHT+IH11d/uzlbF6oT2K+pULvCYo+bR+BgcwrArP5jZFrFue5zZKk3gsmi94ZqjD5PrUsbduuAO7CYV04SRhtslg+g= X-Received: by 2002:a05:6512:3ba5:b0:52c:d819:517e with SMTP id 2adb3069b0e04-53dab2a6343mr1711263e87.30.1731685789846; Fri, 15 Nov 2024 07:49:49 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Torsten_F=C3=B6rtsch?= Date: Fri, 15 Nov 2024 16:49:38 +0100 Message-ID: Subject: Re: DB Files To: Andy Hartman Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000005dd9380626f58477" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005dd9380626f58477 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable PG normally splits table data into 1GB chunks. The number before the dot is called the filenode. You can translate it into a table name by select oid::regclass::text from pg_class where relfilenode=3D'2474695'; I believe there is an option to change that chunk size but you'd have to recompile Postgres. The setting you need to change is called segment_size. See https://www.postgresql.org/docs/current/runtime-config-preset.html On Fri, Nov 15, 2024 at 3:27=E2=80=AFPM Andy Hartman wrote: > I created a new table (V16) and then used SimplySql to take data from > mssql to the new Postgres table. The table is 212gig in size. Myquestion > comes from the files created on the OS(Windows2022 server) I can see lots > of files with the last being: > > 2474695.143 > > They are all 1,048,576kb > > Is this normal behaviour and could I have done something to use fewer > files and larger ones? > > > This table is created in a separate tablespace on a dedicated drive on th= e > windows file system. > > I'm just getting involved in this PostgreSql instance > > THanks. > --0000000000005dd9380626f58477 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
PG normally splits table data into 1GB chunks. The number = before the dot is called the filenode. You can translate it into a table na= me by

select oid::regclass::text from pg_class where rel= filenode=3D'2474695';

I believe there is a= n option to change that chunk size but you'd have to recompile Postgres= . The setting you need to change is called segment_size.

On Fri, Nov 15, 2024 at 3:27=E2=80=AFPM Andy Hartman &= lt;hartman60home@gmail.com&g= t; wrote:
I created a=C2=A0 new table (V16) and then used= SimplySql to take data from mssql=C2=A0to the new Postgres table. The tabl= e is 212gig in size. Myquestion comes from the files created on the OS(Wind= ows2022 server) I can see lots of files with the last being:

2474695= .143

They are all 1,048,576kb=C2=A0
Is this normal behaviour and could I have done something to use fewer = files and larger ones?


This table is created in a separate=C2=A0= tablespace on a dedicated=C2=A0drive on the windows file system.

=C2= =A0I'm just getting involved in this PostgreSql instance=C2=A0

T= Hanks.
--0000000000005dd9380626f58477--