On Mon, 2006-11-27 at 17:58 -0500, Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > On Mon, 2006-11-27 at 17:48 -0500, Tom Lane wrote:
> >> I do not see the point of this. Shall we put equivalent disclaimers
> >> into every single construct that consumes shared memory?
>
> > Stating that it uses shared memory? Absolutely. Stating that you may run
> > out? No, ...
>
> Well, the fact that it uses shared memory is an uninteresting
> implementation detail --- at least, it's uninteresting until you run
> out. When/if that happens, ISTM the error message and HINT are plenty
> good enough to tell you what to do about it. If we tried to document
> every possible error message and appropriate corrective action for same
> the docs would become bloated to the point of unreadability. So to me
> the question is why this particular case deserves a paragraph of its own.
I would agree that it likely does not need a paragraph on its own.
Hmm... but a shared memory reference page? Something that says, "What
uses shared memory with PostgreSQL?" That might be useful.
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
