| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deadlock condition in current sources |
| Date: | 2001-12-18 19:11:55 |
| Message-ID: | 3705826352029646A3E91C53F7189E32518450@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Checkpoint' undo is not used currently so just comment out
> > GetUndoRecPtr call in CreateCheckPoint - we'll find solution later.
>
> I thought about that, but figured you'd object ;-)
>
> One possibility is to do something you had recommended awhile back for
> other reasons: add a spinlock to each PROC structure and use the
> spinlock, rather than SInvalLock, to protect setting and reading of
> xmin, logRec, and related fields. I haven't finished working out all
> the details, though, and this seems like a rather large change to make
> at this late stage of beta. Comments?
Sure - *comment* out GetUndoRecPtr -:)
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Mascari | 2001-12-18 19:13:15 | Re: Concerns about this release |
| Previous Message | Tom Lane | 2001-12-18 19:05:43 | Re: Deadlock condition in current sources |