| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "paulo matadr" <saddoness(at)yahoo(dot)com(dot)br> |
| Cc: | GENERAL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Erro in vaccum |
| Date: | 2008-12-22 18:05:33 |
| Message-ID: | dcc563d10812221005k54ac3e08s626b487eeb0a4fd6@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 22, 2008 at 10:22 AM, paulo matadr <saddoness(at)yahoo(dot)com(dot)br> wrote:
>
> My vacuum was follow error below:
> WARNING: oldest xmin is far in the past
> HINT: Close open transactions soon to avoid wraparound problems.
> No have transactions in locked ,
Transactions don't have to hold locks to cause problems. Generally
speaking you've got an old transaction being held open. what does:
select min(xact_start) from pg_stat_activity;
say?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shane Wright | 2008-12-22 18:16:43 | Using the wrong index (very suboptimal), why? |
| Previous Message | Sebastian Tennant | 2008-12-22 18:02:04 | Re: Ordering returned rows according to a list |