| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | frank <f(dot)callaghan(at)ieee(dot)org> |
| Cc: | Fabrice Scemama <fabrices(at)ximmo(dot)ftd(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is Pg 7.0.x's Locking Mechanism BROKEN? |
| Date: | 2000-07-27 20:23:14 |
| Message-ID: | 9089.964729394@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Frank and Fabrice,
If you aren't having any luck generating a reproducible example of this
problem, you might try recompiling the backend with LOCK_DEBUG defined
in src/include/config.h --- or just do
gmake clean
gmake PROFILE=-DLOCK_DEBUG all
This should produce pretty voluminous quantities of info in the
postmaster's stdout/stderr log. Run the postmaster with -d2 so we
can see the related queries too, and then maybe the log will have enough
info to tell something useful the next time you see it happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Jones | 2000-07-27 23:59:00 | Re: 4 billion record limit? |
| Previous Message | Jesus Aneiros | 2000-07-27 20:02:16 | Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Brenner | 2000-07-27 20:44:52 | Re: Inprise InterBase(R) 6.0 Now Free and Open Source |
| Previous Message | Tom Lane | 2000-07-27 20:14:20 | Questionable coding in proc.c & lock.c |