| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Gene Hart <genekhart(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: vacuum won't fix tx wraparound problem |
| Date: | 2010-06-27 14:30:56 |
| Message-ID: | 10169.1277649056@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> In response to Gene Hart <genekhart(at)gmail(dot)com>:
>> PostgreSQL stand-alone backend 8.4.4
>> backend> vacuum
>> backend> ^D^D
>> exit
> Am I reading this wrong or did you not bother to allow the vacuum to finish?
> Considering there's no command terminator (;) on the vacuum command, it's
> unlikely that it ever actually started to do anything.
No, Gene did it right --- standalone backends have a different command-line
syntax. (I assume also that he observed a suitably long delay before
the second backend> prompt came up...)
I think Scott's idea of ancient prepared transactions is probably the
most likely bet. Roll those back and then vacuum and you'll be OK.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gene Hart | 2010-06-27 16:41:20 | Re: vacuum won't fix tx wraparound problem |
| Previous Message | Bill Moran | 2010-06-27 13:44:55 | Re: vacuum won't fix tx wraparound problem |