Re: Problem with multiple comments - Mailing list pgadmin-support
From | Per Wigren |
---|---|
Subject | Re: Problem with multiple comments |
Date | |
Msg-id | CACjysiXd-cno42wOu3D6y34AM7R3wJY2Eycdb5q5FHyVURi7uw@mail.gmail.com Whole thread Raw |
In response to | Re: Problem with multiple comments (Dave Page <dpage@pgadmin.org>) |
Responses |
Re: Problem with multiple comments
|
List | pgadmin-support |
ok, then the same issue occurs with functions as well because there are the same kind of duplicates in the list of functions.<divclass="gmail_extra"><br /><br /><div class="gmail_quote">2012/12/6 Dave Page <span dir="ltr"><<a href="mailto:dpage@pgadmin.org"target="_blank">dpage@pgadmin.org</a>></span><br /><blockquote class="gmail_quote" style="margin:00 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Dec 6, 2012 at 11:03 AM, PerWigren <<a href="mailto:per.wigren@gmail.com">per.wigren@gmail.com</a>> wrote:<br /> > Yes, I have actually runpg_upgrade on it... Where can I find details about<br /> > this bug?<br /><br /></div>The CHANGELOG just says:<br/><br /> 2012-11-26 MH 1.16.1 Fix query for database descriptions<br /><br /> So I guess the same issue occurswith schemas. I believe it occurs<br /> because pg_upgrade can cause OIDs to be reused in ways not previously<br />seen.<br /><div class="im"><br /> > The same thing happens with 1.16.1.<br /><br /></div>I'll look into it.<br /><divclass="HOEnZb"><div class="h5"><br /> ><br /> > 2012/12/6 Dave Page <<a href="mailto:dpage@pgadmin.org">dpage@pgadmin.org</a>><br/> >><br /> >> On Thu, Dec 6, 2012 at 10:47 AM, PerWigren <<a href="mailto:per.wigren@gmail.com">per.wigren@gmail.com</a>> wrote:<br /> >> > I mailed youthe screenshots.<br /> >> ><br /> >> > I snatched the SQL from pg_log that pgAdmin runs when refreshingthe<br /> >> > list of<br /> >> > schemas and that query also returns these duplicate schemas.So do the<br /> >> > Object List Report html output.<br /> >><br /> >> Hmm, odd. I don't supposeyou've run pg_upgrade on this database have you?<br /> >><br /> >> Magnus fixed a bug similar to thisthe other day (possibly this very<br /> >> one). Can you test 1.16.1 please? I just released it an hour ago.<br/> >><br /> >> > 2012/12/6 Dave Page <<a href="mailto:dpage@pgadmin.org">dpage@pgadmin.org</a>><br/> >> >><br /> >> >> On Thu, Dec 6, 2012at 10:31 AM, Per Wigren <<a href="mailto:per.wigren@gmail.com">per.wigren@gmail.com</a>><br /> >> >>wrote:<br /> >> >> > When querying pg_description for the oid of one schema that has<br /> >>>> > duplicates<br /> >> >> > in pgAdmin I get this:<br /> >> >> ><br /> >>>> > bix_live=# select * from pg_description where objoid = 16458;<br /> >> >> > objoid| classoid | objsubid |<br /> >> >> > description<br /> >> >> ><br /> >> >>><br /> >> >> > --------+----------+----------+--------------------------------------------------------------------------------------------------------<br />>> >> > 16458 | 2615 | 0 | The main comment<br /> >> >> > 16458 | 1259| 1 | some other comment<br /> >> >> > 16458 | 1259 | 2 | yet another comment<br/> >> >> > 16458 | 1259 | 3 | a different comment<br /> >> >> > 16458| 1259 | 4 | another different comment<br /> >> >> > (5 rows)<br /> >> >> ><br/> >> >> > These are the comments that are displayed for the various duplicates<br /> >> >>> in<br /> >> >> > pgAdmin. Only the main comment is suppsed to be there, I don't know<br /> >>>> > where<br /> >> >> > the others come from. The extra comments are the same for all schemas<br/> >> >> > that<br /> >> >> > have duplicates.<br /> >> >><br /> >>>> The rows with objsubid set to something other than 0 are almost<br /> >> >> certainly commentson table columns (the sub ID being the column<br /> >> >> number). That's perfectly normal. I'm stillnot clear where you're<br /> >> >> seeing a problem though - can you show me a screenshot of the affect<br/> >> >> schema in pgAdmin, including both the properties pane showing the<br /> >> >> schemaOID, and the SQL pane?<br /> >> >><br /> >> >> Thanks.<br /> >> >><br /> >>>><br /> >> >> --<br /> >> >> Dave Page<br /> >> >> Blog: <a href="http://pgsnake.blogspot.com"target="_blank">http://pgsnake.blogspot.com</a><br /> >> >> Twitter: @pgsnake<br/> >> >><br /> >> >> EnterpriseDB UK: <a href="http://www.enterprisedb.com" target="_blank">http://www.enterprisedb.com</a><br/> >> >> The Enterprise PostgreSQL Company<br /> >> ><br/> >> ><br /> >><br /> >><br /> >><br /> >> --<br /> >> Dave Page<br /> >>Blog: <a href="http://pgsnake.blogspot.com" target="_blank">http://pgsnake.blogspot.com</a><br /> >> Twitter:@pgsnake<br /> >><br /> >> EnterpriseDB UK: <a href="http://www.enterprisedb.com" target="_blank">http://www.enterprisedb.com</a><br/> >> The Enterprise PostgreSQL Company<br /> ><br /> ><br/><br /><br /><br /> --<br /> Dave Page<br /> Blog: <a href="http://pgsnake.blogspot.com" target="_blank">http://pgsnake.blogspot.com</a><br/> Twitter: @pgsnake<br /><br /> EnterpriseDB UK: <a href="http://www.enterprisedb.com"target="_blank">http://www.enterprisedb.com</a><br /> The Enterprise PostgreSQL Company<br/></div></div></blockquote></div><br /></div>
pgadmin-support by date: