| From: | Timothy Garnett <tgarnett(at)panjiva(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated) |
| Date: | 2015-04-07 22:06:15 |
| Message-ID: | CAPcyiQ1tKyMj348o2-zKQWrGM=vyjOboVog+gF74j5rXw8=Hjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>
>
> > - why didn't vacuum_db -a -F free up more members files?
>
> Are you sure that while the problem was developing the primary
> cluster didn't have any long-running transactions (including those
> left "idle in transaction" or prepared transactions)? Was there a
> checkpoint following the vacuumdb -a -F run?
The vacuum_db was run after we recovered from backup (which involved
restarting the server) so at the time the vacuum_db started there were no
open transactions. There have have been checkpoints since the vacuum_db
finished as well.
In the lead up to the problem there wouldn't have been any transactions
open more then a couple of hours (the oldest members file was over 6 months
old).
Tim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-04-08 04:27:08 | Re: PQexec() hangs on OOM |
| Previous Message | Kevin Grittner | 2015-04-07 21:53:06 | Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated) |