Re: pg_dump -s dumps data?! - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump -s dumps data?!
Date
Msg-id 15160.1327712586@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump -s dumps data?!  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: pg_dump -s dumps data?!  (hubert depesz lubaczewski <depesz@depesz.com>)
Re: pg_dump -s dumps data?!  (hubert depesz lubaczewski <depesz@depesz.com>)
Re: pg_dump -s dumps data?!  (hubert depesz lubaczewski <depesz@depesz.com>)
Re: pg_dump -s dumps data?!  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
hubert depesz lubaczewski <depesz@depesz.com> writes:
> I have weird situation.
> pg 9.1.2, compilet by our own script from source, on 10+ machines.
> on fours machines, pg_dump -s <database_name> - dumps with data!:

> postgres@machine:~$ pg_dump --verbose  --schema-only dbname > q
> ...
> pg_dump: creating TABLE x1
> pg_dump: restoring data for table "x2"
> pg_dump: dumping contents of table x2
> pg_dump: restoring data for table "x3"
> pg_dump: dumping contents of table x3
> ...

> What could be wrong?

Do the command lines actually look exactly like that?

Some platforms are forgiving about violation of the switch-then-argument
order (ie, putting switches after the database name) and some are not.
I seem to recall that Solaris is particularly strange about this,
so what platform(s) are we talking about anyway?

            regards, tom lane

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg_dump -s dumps data?!
Next
From: Tom Lane
Date:
Subject: Re: 9.0.6 "cluster" transient failure ...