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

Re: BUG #1349: Gap in documentation - pg_dump

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Piotr Likus <vpiotr(at)poczta(dot)onet(dot)pl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1349: Gap in documentation - pg_dump
Date: 2004-12-16 21:42:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, Dec 16, 2004 at 20:21:48 +0100,
  Piotr Likus <vpiotr(at)poczta(dot)onet(dot)pl> wrote:
> Yes, maybe it is insecure, but sometimes "quick and dirty" solutions
> are better than no solution at all.
> After all you can add "not recommended" note to this tip.

The official documentation isn't likely to be changed to instruct people
how to incorrectly set up their system.

It may be that there is a deficiency in the pg_dump documentation if you
are expected to know something from another part of the manual that it
may not be obvious that you should know. In that case the answer is
to refer to the other section or to include enough information to
avoid needing to refer to the other section.`

In response to

pgsql-bugs by date

Next:From: Belbin, PeterDate: 2004-12-16 23:15:12
Subject: Re: solaris 10 with gcc 3.3.2
Previous:From: Hesse, HendrikDate: 2004-12-16 15:41:43
Subject: Problem with Upper/Lower Function

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