On Fri, 5 Jan 2001, Tom Lane wrote:

> I just finished running the parallel regress tests with inval.c rigged
> to flush the relcache and syscache at every available opportunity,
> that is anytime we could recognize a shared-cache-inval message from
> another backend (see diff below).  This setup gives a whole new universe
> of meaning to the word "slow" --- it took *three full days* to run the
> standard "make check" procedure, including eighteen hours just to do the
> "vacuum template1" part of initdb.  I kid you not.  But it worked.
> Looks like the unexpected-cache-entry-drop class of problems are indeed
> gone.
Tom, I'm not sure how (or whether) this relates to "alter table" happening
when someone else is doing a SELECT from table. Are you saying that it
should work without any locking or I'm completely off base?

-alex

In response to

• Well, we seem to be proof against cache-inval problems now at 2001-01-05 06:18:47 from Tom Lane

Responses

• Re: Well, we seem to be proof against cache-inval problems now at 2001-01-05 19:14:29 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2001-01-05 19:14:29
	Subject: Re: Well, we seem to be proof against cache-inval problems now
Previous:	From: Alex Pilosov	Date: 2001-01-05 18:50:18
	Subject: Re: running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2