Re: what to do with backend flowchart

I'm currently working on consolidating some of the content on the developer
site with the current web code cvs and am wondering what to do with
http://developer.postgresql.org/docs/pgsql/src/tools/backend/index.html.
This link actually comes right out of the postgresql sources, but it is
actually quite a bit out of date at this point. I guess it might be worth
asking if it is so out of date that it isnt even worth displaying anymore...
it looks usefull to me but I'm not certain how far out of whack it is, just
know that it doesn't match reality at this point. We could have someone
update it and then generate it out of cvs onto the website, but it really
seems like the kind of thing that should live in the web code rather than
core cvs anyway. I'm willing to import it all into the web cvs, and send a
patch removing it from the core cvs if no one objects, lmk.

--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> I'm currently working on consolidating some of the content on the developer
> site with the current web code cvs and am wondering what to do with
> http://developer.postgresql.org/docs/pgsql/src/tools/backend/index.html.
> This link actually comes right out of the postgresql sources, but it is
> actually quite a bit out of date at this point.

At the level of detail that that's giving, it's not all that out of
date; though I agree that it could probably do with a lookthrough.

> know that it doesn't match reality at this point. We could have someone
> update it and then generate it out of cvs onto the website, but it really
> seems like the kind of thing that should live in the web code rather than
> core cvs anyway. I'm willing to import it all into the web cvs, and send a
> patch removing it from the core cvs if no one objects, lmk.

If your objection is that it's not being maintained, then that is no
solution. Once it's out of the source code CVS it is *guaranteed* to
not get updated to track source-code changes.

regards, tom lane

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes
> If your objection is that it's not being maintained, then that is no
> solution. Once it's out of the source code CVS it is *guaranteed* to
> not get updated to track source-code changes.
>

Is it possible that we insert some tags (like doc++ does) into source code
comments and write a small parser to retrieve them automatically and
generate most part of the backend flowchat?

Regards,
Qingqing

On Sunday 20 March 2005 13:24, Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > know that it doesn't match reality at this point. We could have someone
> > update it and then generate it out of cvs onto the website, but it really
> > seems like the kind of thing that should live in the web code rather than
> > core cvs anyway. I'm willing to import it all into the web cvs, and send
> > a patch removing it from the core cvs if no one objects, lmk.
>
> If your objection is that it's not being maintained, then that is no
> solution. Once it's out of the source code CVS it is *guaranteed* to
> not get updated to track source-code changes.
>

My thoughts were that it is certainly easier for us to implement web code that
comes from the web cvs rather than the core cvs, and also that it seems wierd
to have this type of html/graphics living tucked away inside the application
code. You seem to be opposed to moving it though (or at least unconvinced)
so I guess we will work things out on the web side.

--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

I have update the backend flowchart to more closely match current CVS.
The web site pulls from our CVS automatically so it should be updated
soon on the web site.

---------------------------------------------------------------------------

Robert Treat wrote:
> On Sunday 20 March 2005 13:24, Tom Lane wrote:
> > Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > > know that it doesn't match reality at this point. We could have someone
> > > update it and then generate it out of cvs onto the website, but it really
> > > seems like the kind of thing that should live in the web code rather than
> > > core cvs anyway. I'm willing to import it all into the web cvs, and send
> > > a patch removing it from the core cvs if no one objects, lmk.
> >
> > If your objection is that it's not being maintained, then that is no
> > solution. Once it's out of the source code CVS it is *guaranteed* to
> > not get updated to track source-code changes.
> >
>
> My thoughts were that it is certainly easier for us to implement web code that
> comes from the web cvs rather than the core cvs, and also that it seems wierd
> to have this type of html/graphics living tucked away inside the application
> code. You seem to be opposed to moving it though (or at least unconvinced)
> so I guess we will work things out on the web side.
>
> --
> Robert Treat
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>

--
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