Re: Inherited constraints and search paths (was Re: Preserving - Mailing list pgsql-general

From Tom Lane
Subject Re: Inherited constraints and search paths (was Re: Preserving
Date
Msg-id 24635.1116599516@sss.pgh.pa.us
Whole thread Raw
In response to Re: Inherited constraints and search paths (was Re: Preserving  (Berend Tober <btober@seaworthysys.com>)
List pgsql-general
Berend Tober <btober@seaworthysys.com> writes:
> If the pg_dump output produced "SET search_path" statement with the
> complete actual path required to find all objects in subsequent DDL
> statements, my world would be at peace.

We're not doing that, because it's demonstrably impossible :-(.
You can't guarantee that every object in a random collection can be
referenced with an unqualified name.  Consider
    ... CHECK (a.foo(f1) AND b.foo(f1))
ie identically named functions in different schemas.

Even in the cases where it is possible, the infrastructure for it isn't
available to pg_dump, which means there's no hope of a solution like
that being back-ported to 7.3.

            regards, tom lane

pgsql-general by date:

Previous
From: Andreas
Date:
Subject: Re: ODBC connection string-constants A,B,C ?
Next
From: Scott Marlowe
Date:
Subject: Re: numeric precision when raising one numeric to