| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Tim Sailer <tps(at)unslept(dot)org>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Strange Problem |
| Date: | 2016-02-11 17:53:06 |
| Message-ID: | 22095.1455213186@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Thom Brown <thom(at)linux(dot)com> writes:
> There are 2 possibilities I can think of:
> 1) The application which inserts the rows still has the transaction
> open that inserted all the rows, and hasn't yet committed.
> 2) A transaction is open, but another transaction has since deleted
> all the rows and committed, and the open transaction still has
> visibility of the rows, so they can't be cleaned up by a vacuum
> process.
"VACUUM VERBOSE <table>" would likely be informative. I don't think
it will distinguish which of those things has happened, but it would
confirm the idea that there are a bunch of not-visible-to-you rows.
It might be a good idea to check for old prepared transactions, as
well as old idle-in-transaction sessions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Sailer | 2016-02-11 18:13:46 | Re: Strange Problem |
| Previous Message | Thom Brown | 2016-02-11 17:39:52 | Re: Strange Problem |