Re: BUG #2292: Calling conventions in docs

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Adriaan van Os <pgres(at)microbizz(dot)nl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2292: Calling conventions in docs
Date: 2006-03-05 00:54:09
Message-ID: 20060304165009.V38972@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 2 Mar 2006, Adriaan van Os wrote:

> Tom Lane wrote:
>
> > Adriaan van Os <pgres(at)microbizz(dot)nl> writes:
> >> The manual is simply taking an old prejudice as a fact.
> >
> > No, it is stating a fact as as fact. The existence of one
> > counterexample does not disprove the generalization.
>
> Keep dreaming. Ignorance rules the world.

Is your claim that over a signifcant fraction of all such products, the
default setting is such that it would just work (without for example
annotating the function in any way - which is basically a significant
enough barrier to be difficult for many users)? That's what would be
necessary to say that it isn't "often difficult". If the claim is that
this one product makes it easy, that's insufficient to disprove "often
difficult" although we could potentially note things that would make it
easier.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2006-03-05 04:10:18 Re: BUG #2298: Bug using copy
Previous Message Tom Lane 2006-03-04 22:36:25 Re: BUG #2299: pg_dump error w/ renamed primary keys