| From: | Andy Hartman <hartman60home(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | DB Files |
| Date: | 2024-11-15 14:27:36 |
| Message-ID: | CAEZv3coR69Kjtnd1oDpp-AhwQOrWcW7_4CMH0JQLFcndoP-Q0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 the
windows file system.
I'm just getting involved in this PostgreSql instance
THanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Torsten Förtsch | 2024-11-15 15:28:06 | Re: Validating check constraints without a table scan? |
| Previous Message | Laurenz Albe | 2024-11-15 08:44:08 | Re: Validating check constraints without a table scan? |