| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, JC Praud <brutaltruth42(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: auto truncate/vacuum full |
| Date: | 2009-10-27 20:52:59 |
| Message-ID: | 6032.1256676779@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Tue, 27 Oct 2009, Tom Lane wrote:
>> The issue I can see is that we might never be able to complete any
>> truncation if there's a lot of potentially removable pages and a pretty
>> steady flow of conflicting lock attempts. But that would result in
>> failure to remove bloat, not stoppage of conflicting queries.
> That's exactly it.
That might be exactly what's worrying *you*, but my point was that it
doesn't appear to explain the OP's complaint. Whatever issue he has
got is something else.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Little, Douglas | 2009-10-27 21:31:40 | Re: Pgadmin support for writing files or psql \copy command |
| Previous Message | Tom Lane | 2009-10-27 20:47:53 | Re: auto truncate/vacuum full |