|
I've manage to generate another 359 WAL files in a 10 minute
span yesterday (now only 357 remain and I suspect they will
wither away as before). Are these being held simply because of
the high max_wal_size value? This is a development environment, wherein I'm loading 4M+
records, first into 41 staging tables 100K rows per. In a loop
over each staging table, the data is then placed into
application tables via selects. First select * into "matching
table" then select id into intersection record (id, fixed
groupId). Each such iteration is in it's own transaction. I
have dropped and recreate this same database numerous times
working my way up from 100K to 4M records, dialing in
application parameters according to number of primary records.
I have not, however, dropped the last incarnation. |
