Re: blatantly a bug in the documentation

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Dave Page" <dpage(at)pgadmin(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: blatantly a bug in the documentation
Date: 2008-11-24 14:37:49
Message-ID: b42b73150811240637r52e21e1foabe62704ce737fdf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 24, 2008 at 9:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Dave Page wrote:
>>> It might also be useful to create such a database at initdb time so
>>> newbies have something interesting to look at right away.
>
>> No, there is no need to clutter every installation in the world with
>> such a database. You could make it an addon module, or a pgfoundry project.
>
> The whole thing strikes me as extreme overkill, not to mention a
> misunderstanding of what an example is supposed to be for. If we're
> going to insist that every example in the docs work when
> copied-and-pasted into an empty database, then simple and to-the-point
> examples will be history. Instead of one-liners we'll have clutter.

Clutter is the problem. The cs_log functions in the example do not
serve any purpose that is helpful to describe a for loop. They serve
no real purpose...why not 'raise notice' or just remove them? It
should be clear to distinguish from real and non-real elements.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-24 14:37:59 Re: Visibility map, partial vacuums
Previous Message A. Kretschmer 2008-11-24 14:29:33 Re: blatantly a bug in the documentation