| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
| Cc: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Joerg Hessdoerfer <Joerg(dot)Hessdoerfer(at)sea-gmbh(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Continuous inserts... |
| Date: | 2000-08-22 18:16:20 |
| Message-ID: | 13720.966968180@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Jan Wieck <janwieck(at)Yahoo(dot)com> writes:
> I haven't looked at the code, but pg_class only has a boolean
> telling if a class has rules or not. Could it be that adding
> more rules (or dropping just a few instead of all) doesn't
> update the pg_class tuple, thus the syscache for the table
> isn't invalidated and other backends continue to use the old
> information instead of rescanning pg_rewrite?
This is done correctly in current sources --- see
setRelhasrulesInRelation(). However I recall having dorked with that
code not long ago, and I forget what it looked like before. Perhaps
7.0.* is broken in this respect? Would think people would have noticed,
though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2000-08-22 18:31:31 | Re: Continuous inserts... |
| Previous Message | Tom Lane | 2000-08-22 17:15:20 | Re: Null function parameters |