| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tim Sailer <tps(at)unslept(dot)org> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Strange Problem |
| Date: | 2016-02-11 18:55:51 |
| Message-ID: | 24201.1455216951@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Tim Sailer <tps(at)unslept(dot)org> writes:
> On 02/11/2016 09:53 AM, Tom Lane wrote:
>> "VACUUM VERBOSE <table>" would likely be informative.
> Ugh. I saw a slew of "suspending truncate due to conflicting lock
> request" scroll up the screen, along with lines like "truncated 4928 to
> 1376 pages" all the say down to "truncated 1376 to 0 pages".
> I'm guessing that my table is now empty for some reason. Sigh.
Well, it was logically empty before, now it's physically empty too.
So what this confirms is that there is *not* a question of uncommitted
transactions or anything like that. At this point I'd be looking for
client-side problems in your data insertion procedures.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shmagi Kavtaradze | 2016-02-15 14:17:03 | postgres version problem |
| Previous Message | Tim Sailer | 2016-02-11 18:13:46 | Re: Strange Problem |