| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Whitter" <dwhitter(at)intern(dot)solution-x(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump creates bad dump / pgadmin crash issue |
| Date: | 2006-01-09 21:19:39 |
| Message-ID: | 8301.1136841579@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Daniel Whitter" <dwhitter(at)intern(dot)solution-x(dot)com> writes:
> If I do the following things a bad dump will be created that can't be
> restored (using pgadmin3, pg_dump and pg_restore or psql).
> There's also a issue that pgadmin crash.
You should report the pgadmin crash to the pgadmin people (who may or
may not follow this list closely). The dump problem is a pg_dump bug
which I've just fixed. Apparently you're the first to ever try dumping
an operator definition that contains a cross-schema operator reference :-(.
There should be an OPERATOR() decoration around those names, but pg_dump
didn't know that ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ari Kahn | 2006-01-09 22:00:09 | psql(18967) malloc: *** vm_allocate(size=8421376) failed (error code=3) |
| Previous Message | Matthew Peter | 2006-01-09 21:01:33 | Re: plpgsql question |