On Tue, 2013-01-08 at 19:55 -0700, Josh Kupershmidt wrote:
> On Mon, Jan 7, 2013 at 8:12 PM, Peter Eisentraut wrote:
> > On Sat, 2013-01-05 at 15:34 +0100, Magnus Hagander wrote:
> >> On Fri, Jan 4, 2013 at 3:36 AM, Josh Kupershmidt
> >> wrote:
> >> > I propose slimming down the pg_dump README,
On Mon, Jan 7, 2013 at 8:12 PM, Peter Eisentraut wrote:
> On Sat, 2013-01-05 at 15:34 +0100, Magnus Hagander wrote:
>> On Fri, Jan 4, 2013 at 3:36 AM, Josh Kupershmidt wrote:
>> > I propose slimming down the pg_dump README, keeping intact the
>> > introductory notes and details of the tar format.
On Sat, 2013-01-05 at 15:34 +0100, Magnus Hagander wrote:
> On Fri, Jan 4, 2013 at 3:36 AM, Josh Kupershmidt wrote:
> > I propose slimming down the pg_dump README, keeping intact the
> > introductory notes and details of the tar format.
>
> Do we need to keep it at all, really? Certainly the intr
On Sat, Jan 5, 2013 at 7:34 AM, Magnus Hagander wrote:
> On Fri, Jan 4, 2013 at 3:36 AM, Josh Kupershmidt wrote:
> Do we need to keep it at all, really? Certainly the introductory part
> is covered in the main documentation already...
Pretty much. (I did find note #2 mildly interesting.)
> I be
On Fri, Jan 4, 2013 at 3:36 AM, Josh Kupershmidt wrote:
> The ./src/bin/pg_dump README contains several inoperable examples.
> First, this suggestion:
>
> | or to list tables:
> |
> | pg_restore --table | less
>
> seems bogus, i.e. the --table option requires an argument specifing
> which
The ./src/bin/pg_dump README contains several inoperable examples.
First, this suggestion:
| or to list tables:
|
| pg_restore --table | less
seems bogus, i.e. the --table option requires an argument specifing
which table to restore, and does not "list tables". Next, this
suggested comma
