| From: | Kevin Barnard <kevin(dot)barnard(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pgsql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Vacuum message |
| Date: | 2004-11-11 23:25:00 |
| Message-ID: | b068057c041111152566d5b327@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 11 Nov 2004 13:56:48 -0500, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Were they both VACUUM ANALYZEs? There's a known gotcha that if you
> ANALYZE the same table concurrently in two different sessions, one
> of them can fail this way when it goes to update the pg_statistic
> entries. (Harmless, but annoying.) I don't know of any cause for
> this message from a plain VACUUM though.
>
> regards, tom lane
>
That's what it is I have cron jobs running over each other during heavy load.
Thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2004-11-11 23:29:38 | Re: invalid page header in block 52979 of relation "pg_attribute" |
| Previous Message | Terry Lee Tucker | 2004-11-11 23:24:30 | Re: OID Question |