Re: BUG #7842: pg_dump scripts view to table - Mailing list pgsql-bugs
From | Maciej Łopuszański |
---|---|
Subject | Re: BUG #7842: pg_dump scripts view to table |
Date | |
Msg-id | 510F90E1.1090503@oleofarm.com Whole thread Raw |
In response to | Re: BUG #7842: pg_dump scripts view to table (Tom Lane <tgl@sss.pgh.pa.us>) |
List | pgsql-bugs |
why?<br /><br /> because 1 on views didnt recreate after restoring from backup, we had a table instead of view. that meansincomplete backup without even our knowledge (no warn,error), if its not a bug what other word would be better to describethis?<br /><br /> and now the funny part:<br /> I deleted and created this view(and dependant views) from the samedefinition it was stored in pg, and the problem just vanished....<br /><br /> this view now is properly stored by pg_dump, and properly restored by psql.<br /><br /><br /><div class="moz-cite-prefix">W dniu 01.02.2013 16:06, Tom Lane pisze:<br/></div><blockquote cite="mid:14030.1359731218@sss.pgh.pa.us" type="cite"><pre wrap="">Maciej Łopuszański <a class="moz-txt-link-rfc2396E"href="mailto:lopuszanski@oleofarm.com"><lopuszanski@oleofarm.com></a> writes: </pre><blockquote type="cite"><pre wrap="">is there a way to find exactly what object/table/column creates this circular dependency? </pre></blockquote><pre wrap=""> 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'::regclass or 'viewname'::regtype. </pre><blockquote type="cite"><pre wrap="">pg_dumb even in verbose mode does not warn/error of this situation. </pre></blockquote><pre wrap=""> Why should it? This isn't a bug, this is merely an implementation detail. regards, tom lane </pre></blockquote><br /><div class="moz-signature">-- <br /><span style="color: #004385; font-family: verdana; font-size: 12px"> Maciej Łopuszański<br /> Programista<br /> mobile: +48 797 119 384<br /> e-mail: <a class="moz-txt-link-abbreviated"href="mailto:lopuszanski@oleofarm.com">lopuszanski@oleofarm.com</a><br /></span><br /><imgalt="" border="0" height="122" src="cid:part1.00080507.04080902@oleofarm.com" width="300" /><br /><span style="color:#004385; font-family: verdana; font-size: 11px"> Oleofarm Sp. z o.o., ul. Fabryczna 16, 55-080 Pietrzykowice<br/> tel. +48 71 316 94 55, fax. +48 71 316 94 57, <a href="http://www.oleofarm.com.pl/">www.oleofarm.com.pl</a><br/> NIP: 896-13-78-324, REGON: 933023467<br /><br /> Sąd Rejonowydla Wrocławia Fabrycznej we Wrocławiu , VI Wydział Gospodarczy <br /> Krajowego Rejestru Sądowego pod numerem KRS218272, kapitał zakładowy: 50 000 zł</span><br /><br /><span style="color: #666666; font-family: verdana; font-size: 10px"> Zawarte w niniejszej wiadomości lub załączonym dokumencie informacje są POUFNE<br /> i przeznaczone tylko dlaoznaczonego adresata. Rozpowszechnianie, ujawnianie <br /> i kopiowanie tych informacji jest zabronione. Jeżeli niniejszawiadomość trafiła <br /> do Państwa przez pomyłkę, bardzo prosimy o powiadomienie nas o tym fakcie <br /> i odesłaniedokumentu lub natychmiastowe jego zniszczenie. <br /><br /> The information contained in the e-mail or attacheddocument is CONFIDENTIAL <br /> and is intended only for the use of the individual to whom it is addressed. <br />If you are not the intended recipient or employee responsible to deliver to the <br /> intended recipient, you are herebynotified that any dissemination, distribution <br /> or copying of the communication is strictly prohibited. If youhave received <br /> the e-mail in error, please immediately notify us and return the original message <br /> to us atthe address above or destroy it. </span></div>
pgsql-bugs by date: