| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: more concurrency information in the documentation |
| Date: | 2005-03-14 19:43:21 |
| Message-ID: | 200503141943.j2EJhLP22438@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nguyen Hai | 2005-03-15 23:07:34 | replace palloc/pfree with malloc/free |
| Previous Message | Merlin Moncure | 2005-03-14 19:15:16 | Re: more concurrency information in the documentation |