| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 7.2.3 vacuum bug |
| Date: | 2002-10-31 20:23:08 |
| Message-ID: | 1036095788.94263.47.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2002-10-31 at 13:03, Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > Found another:
> > ERROR: cannot find attribute 2 of relation pg_temp_12100_0
>
> Can you reproduce that?
>
> It could be that this just represents someone's temp table deletion
> committing while VACUUM is partway through trying to build a relcache
> entry to open the relation. If so, it is only another manifestation
> of the should-lock-before-relation-open problem.
Yes, but not easily (very timing dependent), takes a lot of worker
processes to throw it. So it's likely a part of the locking issue.
--
Rod Taylor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Tishler | 2002-10-31 21:33:57 | Re: ipc-daemon |
| Previous Message | Jason Tishler | 2002-10-31 20:18:31 | Re: ipc-daemon |