| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] md.c is feeling much better now, thank you |
| Date: | 1999-09-02 14:43:33 |
| Message-ID: | 9155.936283413@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> I think that, based on this, the changes should be back'd out of v6.5.2
> until further testing and analysis can be done.
If we can't find a solution to the inval-too-late problem pronto,
what we can do is comment out the FileUnlink call in mdtruncate.
I don't see a need to back out the other fixes in md.c.
But I think we ought to fix the underlying problem, not this symptom.
What we now see is that after one backend has done something that
requires invalidating a relcache entry, another backend is able
to complete an entire query using the *old* relcache info before it
notices the shared-inval signal. That's got to have bad consequences
for more than just md.c.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-09-02 14:55:29 | Re: [HACKERS] Odd problem with pg_class ... |
| Previous Message | Leon | 1999-09-02 14:38:43 | Re: [HACKERS] Postgres' lexer |