MIME-Version: 1.0
References: <CAEZv3coR69Kjtnd1oDpp-AhwQOrWcW7_4CMH0JQLFcndoP-Q0g@mail.gmail.com>
 <3266a0a3-4de9-4214-8c4d-dd99b9074e40@aklaver.com>
In-Reply-To: <3266a0a3-4de9-4214-8c4d-dd99b9074e40@aklaver.com>
From: Andy Hartman <hartman60home@gmail.com>
Date: Fri, 15 Nov 2024 10:49:57 -0500
Message-ID: <CAEZv3cqtKUQ8ip=AZPULTJKXvwXLC=whfyVMmtBX9mM5_QCWJA@mail.gmail.com>
Subject: Re: DB Files
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000758fac0626f58565"
Archived-At: <https://www.postgresql.org/message-id/CAEZv3cqtKUQ8ip%3DAZPULTJKXvwXLC%3DwhfyVMmtBX9mM5_QCWJA%40mail.gmail.com>
Precedence: bulk

--000000000000758fac0626f58565
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks... I just found that myself... so normal behavior then...

On Fri, Nov 15, 2024 at 10:47=E2=80=AFAM Adrian Klaver <adrian.klaver@aklav=
er.com>
wrote:

> On 11/15/24 06:27, 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. Myquestio=
n
> > 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?
>
> Read:
>
> https://www.postgresql.org/docs/current/storage-file-layout.html
>
> [...]
>
> "When a table or index exceeds 1 GB, it is divided into gigabyte-sized
> segments. The first segment's file name is the same as the filenode;
> subsequent segments are named filenode.1, filenode.2, etc. This
> arrangement avoids problems on platforms that have file size
> limitations. (Actually, 1 GB is just the default segment size. The
> segment size can be adjusted using the configuration option
> --with-segsize when building PostgreSQL.) In principle, free space map
> and visibility map forks could require multiple segments as well, though
> this is unlikely to happen in practice."
>
> [...]
>
> >
> >
> > This table is created in a separate tablespace on a dedicated drive on
> > the windows file system.
> >
> >   I'm just getting involved in this PostgreSql instance
> >
> > THanks.
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
>

--000000000000758fac0626f58565
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks... I just found that myself... so normal behavior t=
hen...</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Fri, Nov 15, 2024 at 10:47=E2=80=AFAM Adrian Klaver &lt;<a href=3D=
"mailto:adrian.klaver@aklaver.com">adrian.klaver@aklaver.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 11/15/24 06:=
27, Andy Hartman wrote:<br>
&gt; I created a=C2=A0 new table (V16) and then used SimplySql to take data=
 from <br>
&gt; mssql=C2=A0to the new Postgres table. The table is 212gig in size. Myq=
uestion <br>
&gt; comes from the files created on the OS(Windows2022 server) I can see <=
br>
&gt; lots of files with the last being:<br>
&gt; <br>
&gt; 2474695.143<br>
&gt; <br>
&gt; They are all 1,048,576kb<br>
&gt; <br>
&gt; Is this normal behaviour and could I have done something to use fewer =
<br>
&gt; files and larger ones?<br>
<br>
Read:<br>
<br>
<a href=3D"https://www.postgresql.org/docs/current/storage-file-layout.html=
" rel=3D"noreferrer" target=3D"_blank">https://www.postgresql.org/docs/curr=
ent/storage-file-layout.html</a><br>
<br>
[...]<br>
<br>
&quot;When a table or index exceeds 1 GB, it is divided into gigabyte-sized=
 <br>
segments. The first segment&#39;s file name is the same as the filenode; <b=
r>
subsequent segments are named filenode.1, filenode.2, etc. This <br>
arrangement avoids problems on platforms that have file size <br>
limitations. (Actually, 1 GB is just the default segment size. The <br>
segment size can be adjusted using the configuration option <br>
--with-segsize when building PostgreSQL.) In principle, free space map <br>
and visibility map forks could require multiple segments as well, though <b=
r>
this is unlikely to happen in practice.&quot;<br>
<br>
[...]<br>
<br>
&gt; <br>
&gt; <br>
&gt; This table is created in a separate=C2=A0tablespace on a dedicated=C2=
=A0drive on <br>
&gt; the windows file system.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0I&#39;m just getting involved in this PostgreSql instance<=
br>
&gt; <br>
&gt; THanks.<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
<br>
</blockquote></div>

--000000000000758fac0626f58565--