From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | Rene Romero Benavides <rene(dot)romero(dot)b(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: stale WAL files? |
Date: | 2019-04-10 18:12:13 |
Message-ID: | 04f4bc5d-be30-c1da-4d5c-db0f71b20324@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> As per your configuration :
> max_wal_size = 50GB
> this seems to be the cause for the WAL files piling up.
>
> this has been declared twice, the last one is taking effect.
> --
> El genio es 1% inspiración y 99% transpiración.
> Thomas Alva Edison
> http://pglearn.blogspot.mx/
>
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Michel Pelletier | 2019-04-10 18:55:50 | Re: How to use full-text search URL parser to filter query results by domain name? |
Previous Message | Thomas Kellerer | 2019-04-10 16:20:59 | Re: pg_indexes doesn't show indexes for partitioned tables - bug or intended? |