I barely understand the items sometimes.
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can this now be marked as done?
> * Modification of pg_class can happen while table in use by another
> backend. Might lead to MVCC inside
No? :-)
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can this now be marked as done?
> * Modification of pg_class can happen while table in use by another
> backend. Might lead to MVCC inside of syscache
> >>
> >> I'm no
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Can this now be marked as done?
> > * Modification of pg_class can happen while table in use by another
> > backend. Might lead to MVCC inside of syscache
>
> I'm not sure. Do you have any record of what the concern was, in
> detail? I
Can this now be marked as done?
* Modification of pg_class can happen while table in use by another
backend. Might lead to MVCC inside of syscache
> I just finished running the parallel regress tests with inval.c rigged
> to flush the relcache and syscache at every available opportun
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
