Where are we on this?
---
Tom Lane wrote:
Kris Jurka [EMAIL PROTECTED] writes:
Possibly the most correct solution is to assign the name public to the
dummy schema that pg_dump creates internally when talking to a
When running pg_dump --clean against a server that doesn't have schemas
the namespace is blank and ends up producing a dump full off things like:
DROP TABLE .tab;
The attached patch only includes a schema if one exists. There are
numerous comments about the DROPs needing to be fully qualified
When running pg_dump --clean against a server that doesn't have schemas
the namespace is blank and ends up producing a dump full off things like:
DROP TABLE .tab;
Since the person is dumping using 7.5 pg_dump, presumably they will be
restoring to 7.5, and it should be:
DROP TABLE public.tab;
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
When running pg_dump --clean against a server that doesn't have schemas
the namespace is blank and ends up producing a dump full off things like:
DROP TABLE .tab;
Since the person is dumping using 7.5 pg_dump, presumably they will be
On Thu, 24 Jun 2004, Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
When running pg_dump --clean against a server that doesn't have schemas
the namespace is blank and ends up producing a dump full off things like:
DROP TABLE .tab;
Since the person is dumping
Kris Jurka [EMAIL PROTECTED] writes:
Possibly the most correct solution is to assign the name public to the
dummy schema that pg_dump creates internally when talking to a pre-7.3
server.
I was considering that they might want to restore the dump into another
schema and that would be easier