Re: pg_dump "Access is denied" Windows 10

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: robinwin(at)tpg(dot)com(dot)au
Cc: "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org>
Subject: Re: pg_dump "Access is denied" Windows 10
Date: 2017-07-21 02:17:53
Message-ID: CAKFQuwYfP_M=+_4cqzCXwgQijujDxnSTL305zvcfS14hoqHd8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thu, Jul 20, 2017 at 6:37 PM, <robinwin(at)tpg(dot)com(dot)au> wrote:

> Could you include in this documentation possible problems and fixes to this
> because I can&#39;t find any.
>

​tl;dr - the documentation is not a good place for such content.​

​It would be helpful if you'd get diagnostic help on the -general mailing
list first. If, after you figure out what the problem and solution are,
you have an idea as to how to improve the documentation (or wiki, see
below) you should then submit said recommendation or update the wiki as
appropriate.

The ability to envision possible problems is a limited ability and given
that your particular complaint seems infrequent on these lists its quite
probable that even if we had such a section (especially given the
assumption that we'd start off documenting problems with pg_dump instead of
some other aspect of the application suite) that your specific
cause/solution would not be covered. Plus, frankly, the documentation
doesn't go to any great efforts to deal with run-time environment problems
(and its update schedule is not really suited for such). A more
appropriate forum would be our wiki.
https://wiki.postgresql.org/wiki/Main_Page

David J.​

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message gorka.gil 2017-07-21 10:18:23 remove shmmax example in Linux section
Previous Message robinwin 2017-07-21 01:37:49 pg_dump "Access is denied" Windows 10