Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Can you show me a non-broken
>> situation where pg_dump needs to resort to view shells?
> Well then shouldn't we just ban you from creating a view that creates a
> circular dependency?
I dunno. My question is exactly about whether there are
and a dump that orders the two views arbitrarily. We can certainly add
code to do something different, but are there any real-world cases where
this is needed? The above example seems more than slightly made-up.
The views aren't actually functional anyway (trying to use either would
result in an
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Please provide example cases.
> create view v1 as select 1;
> create view v2 as select 1 + (select * from v1);
> create or replace view v1 as select * from v2;
> It seems to me that the only way to solve that one is to dump 'view
> shells'.
There's not currently any code for that, though I imagine we could
invent some at need. Please provide example cases.
create view v1 as select 1;
create view v2 as select 1 + (select * from v1);
create or replace view v1 as select * from v2;
It seems to me that the only way to solve that one is to
> I'm interested to know how you deal with circular dependencies in Views
> and Functions?
There's not currently any code for that, though I imagine we could
invent some at need. Please provide example cases.
> Also, what happens if I delete a key dependency from my pg_depend table
> manually?
Hey Tom,
I have committed some fairly wide-ranging revisions to pg_dump to make
it dump database objects in a "safe" order according to the dependency
information available from pg_depend. While I know that I have fixed
a lot of previously-broken cases, it's hardly unlikely that I've broken
some
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> I tried with 7.3.3 and got error:
> ./pg_dump: relocation error: ./pg_dump: undefined symbol: get_progname
You have a problem with linking to the wrong version of libpq.so.
regards, tom lane
---(end of br
On Sat, 6 Dec 2003, Tom Lane wrote:
> I have committed some fairly wide-ranging revisions to pg_dump to make
> it dump database objects in a "safe" order according to the dependency
> information available from pg_depend. While I know that I have fixed
> a lot of previously-broken cases, it's har
I have committed some fairly wide-ranging revisions to pg_dump to make
it dump database objects in a "safe" order according to the dependency
information available from pg_depend. While I know that I have fixed
a lot of previously-broken cases, it's hardly unlikely that I've broken
some things too
