Skip site navigation (1) Skip section navigation (2)

Re: blatantly a bug in the documentation

From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 15:04:01
Message-ID: 603c8f070811240704y285eeaacn4c34b82c713ab9b@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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.

+1 for RAISE NOTICE.

...Robert

In response to

pgsql-hackers by date

Next:From: Marko KreenDate: 2008-11-24 15:07:04
Subject: [bugfix] DISCARD ALL does not release advisory locks
Previous:From: Magnus HaganderDate: 2008-11-24 15:00:42
Subject: Re: [PATCHES] Solve a problem of LC_TIME of windows.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group