Alvaro Herrera wrote:
I think getting rid of the FAQ completely is not necessarily a good
idea; it seems useful as a collection of interesting questions. Moving
the contents to new pages is probably OK. Also, as the answers mature
on the Wiki, perhaps it'd be possible to move them to the SGML d
Peter Eisentraut wrote:
> Alvaro Herrera wrote:
>> However I wonder how much value there really is in the developer's FAQ,
>> considering that some answers seem rather poor. For example the
>> answer on ereport() was wrong, and nobody ever pointed it out. The
>> answer on palloc/pfree is very inc
On Fri, Sep 12, 2008 at 10:29:54AM +0300, Peter Eisentraut wrote:
> Alvaro Herrera wrote:
>> However I wonder how much value there really is in the developer's
>> FAQ, considering that some answers seem rather poor. For example
>> the answer on ereport() was wrong, and nobody ever pointed it out.
Alvaro Herrera wrote:
However I wonder how much value there really is in the developer's FAQ,
considering that some answers seem rather poor. For example the
answer on ereport() was wrong, and nobody ever pointed it out. The
answer on palloc/pfree is very incomplete too.
I think the developer
Peter Eisentraut wrote:
> Alvaro Herrera wrote:
>> So I went ahead and moved its mention to a separate question, where it
>> has a lot more visibility. (I also added an URL to anoncvs, where
>> people can see it more readily.)
>
> Perhaps the low visibility also has to do with the fact that
> do
Alvaro Herrera wrote:
So I went ahead and moved its mention to a separate question, where it
has a lot more visibility. (I also added an URL to anoncvs, where
people can see it more readily.)
Perhaps the low visibility also has to do with the fact that
documentation is hidden under "tools".
On Mon, 8 Sep 2008, Bruce Momjian wrote:
I don't think much changes at the flow chart level from release to
release so it would fine if it was just CVS HEAD. I also don't think
many people do back-branch development.
It's easy with Mediawiki to both 1) see the old version for those
situation
Alvaro Herrera wrote:
> So I just noticed that we have a description of the Pg innards in the
> sourcecode, complete with a flowchart and all, at src/tools/backend.
> I had already seen this graph years ago; what shocked me the most was
> finding out that there's a pointer to it in the Developer's
Alvaro Herrera wrote:
> So I just noticed that we have a description of the Pg innards in the
> sourcecode, complete with a flowchart and all, at src/tools/backend.
> I had already seen this graph years ago; what shocked me the most was
> finding out that there's a pointer to it in the Developer's
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > What I'm wondering right now is what's the value of having this stuff
> > in the source code at all.
>
> So it will be in sync with the version of the source it's with?
> If we move it to the wiki it'll be impractical to maintain the
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> What I'm wondering right now is what's the value of having this stuff
> in the source code at all.
So it will be in sync with the version of the source it's with?
If we move it to the wiki it'll be impractical to maintain the info
for anything except HE
So I just noticed that we have a description of the Pg innards in the
sourcecode, complete with a flowchart and all, at src/tools/backend.
I had already seen this graph years ago; what shocked me the most was
finding out that there's a pointer to it in the Developer's FAQ, in a
question that's abso
12 matches
Mail list logo
