From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump -s dumps data?! |
Date: | 2012-01-28 01:03:06 |
Message-ID: | 15160.1327712586@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
hubert depesz lubaczewski <depesz(at)depesz(dot)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(at)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-01-28 08:45:41 | Re: 9.0.6 "cluster" transient failure ... |
Previous Message | Adrian Klaver | 2012-01-27 23:11:32 | Re: pg_dump -s dumps data?! |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2012-01-28 01:21:59 | Re: CLOG contention, part 2 |
Previous Message | Jeff Davis | 2012-01-28 00:19:41 | initdb and fsync |