Merlin Moncure wrote: > > > than something we would have in our docs. Perhaps we should like to > > more outside documentation, but the URL you provided is so > content-light > > that I would not recommend it. > > hm, I'm not so sure I would agree with that sentiment. Good information > on how to deal with database concurrency issues seems to me to be pretty > hard to find. Let me ask you this, do you think the current > documentation on database concurrency could be improved, and if so, how? > Right now, it is fairly abstract and technical, and that may be a good > thing.
Yea, I guess we could improve it, but looking at cost/benefit, I am not sure how much sense it makes to add stuff that is not PostgreSQL-specific. -- Bruce Momjian | http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
