why?
because 1 on views didnt recreate after restoring from backup, we
had a table instead of view. that means incomplete backup without
even our knowledge (no warn,error), if its not a bug what other word
would be better to describe this?
and now the funny
=?UTF-8?B?TWFjaWVqIMWBb3B1c3phxYRza2k=?= writes:
> is there a way to find exactly what object/table/column creates this
> circular dependency?
Look into pg_depend for entries referencing the view or the view's
rowtype. (Offhand I'd bet it's the latter.) So the refobjid would
be 'viewname'::reg
is there a way to find exactly what object/table/column creates this
circular dependency?
pg_dumb even in verbose mode does not warn/error of this situation. I
managed to find this by testing copy of production db(this should be
reported by pg_dump). also there is nothing fancy about this 'vie
lopuszan...@oleofarm.com writes:
> 1. after using pg_dump to dump WHOLE database to file, 1 of views 'turned'
> into a table.
> so there is no 'create or replace VIEW ...' with definition, but
> instead:
> its scripted as 'create TABLE ..' and definition.(in file that
> pg_dump cr
The following bug has been logged on the website:
Bug reference: 7842
Logged by: Maciej Łopuszański
Email address: lopuszan...@oleofarm.com
PostgreSQL version: 9.1.7
Operating system: ubuntu 12.04
Description:
hello,
1. after using pg_dump to dump WHOLE database to fi
