Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Protocol Message Graph
- From: Simon Riggs <simon(at)2ndquadrant(dot)com>
- To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- Cc: Agent M <agentm(at)themactionfaction(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Protocol Message Graph
- Date: Tue, 25 Apr 2006 13:40:02 +0100
- Message-id: <1145968802(dot)4317(dot)237(dot)camel(at)localhost(dot)localdomain>
On Sun, 2006-04-23 at 18:43 -0400, Alvaro Herrera wrote: > Agent M wrote: > > I have created a directed graph using graphviz that shows the message > > flow/event stream. Perhaps this will be helpful to someone. Of course, > > corrections are also welcome. Thats a good start. > Maybe it would make more sense to have a graph of states, and the edges > would indicate what messages are sent to change from one state to > another. Yes, that would be better. It would be good to do the same for LWLock states, to help check for deadlock possibilities. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
- References:
- Protocol Message Graph
- From: Agent M
- Re: Protocol Message Graph
- From: Alvaro Herrera
- Protocol Message Graph
- Prev by Date: Re: Google SoC--Idea Request
- Next by Date: Re: TODO Item: ACL_CONNECT
- Previous by thread: Re: Protocol Message Graph
- Next by thread: Can't commit due to perl upgrade
- Indexes: