From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Berend Tober <btober(at)seaworthysys(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Inherited constraints and search paths (was Re: Preserving |
Date: | 2005-05-20 14:31:56 |
Message-ID: | 24635.1116599516@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Berend Tober <btober(at)seaworthysys(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-05-20 15:06:57 | Re: numeric precision when raising one numeric to |
Previous Message | Andreas | 2005-05-20 14:19:21 | Re: ODBC connection string-constants A,B,C ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-05-20 14:43:46 | Re: Learning curves and such (was Re: pgFoundry) |
Previous Message | Alvaro Herrera | 2005-05-20 14:28:07 | Re: 8.02 rpm error |