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
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Robert Treat
> Sent: 21 March 2005 19:05
> To: Tom Lane
> Cc: pgsql-hackers@postgresql.org; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] what to do with backend flowchart
>
&g
On Sunday 20 March 2005 13:24, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> 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 t
"Tom Lane" <[EMAIL PROTECTED]> 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 sou
Robert Treat <[EMAIL PROTECTED]> 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 righ
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
actua
