Thread: pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18

pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18

From
"Gary Clarke (M4 Systems Ltd)"
Date:
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36">Helloto pgadmin dev team </span><p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"TrebuchetMS","sans-serif";color:#230C36">(nice app by the way)</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36"> </span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36">I noticed this
pgadminbug in beta version 2 – </span><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36">isstill present in beta version 4 released yesterday.</span><p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"TrebuchetMS","sans-serif";color:#230C36"> </span><p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"TrebuchetMS","sans-serif";color:#230C36">Not critical but I thought would be worth
advisingyou.</span><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36"> </span><pclass="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36">whenI try to – object browse – pg_catalog – in any database – I get error notice - row
number19 is out of range 0..18</span><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36"> </span><pclass="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36">about25 clicks required to get past error message – then browses ok</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36"> </span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36">pg admin 1.16
beta4  - Running on 64 bit windows</span><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36"> </span><pclass="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet
MS","sans-serif";color:#230C36">postgresv 9.2 beta 3 – running on Ubuntu 12.04 – on virtual box v1.18</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36"> </span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36">postgres build
hasbeen changed - increased max for object identifiers to 256 character </span><p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"TrebuchetMS","sans-serif";color:#230C36"> </span><p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"TrebuchetMS","sans-serif";color:#230C36">NAMEDATALEN  64 to 256</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36"> </span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36">Regards</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36"> </span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36">Gary</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#230C36"> </span><p
class="MsoNormal"><b><i><spanstyle="font-size:9.0pt;font-family:"Trebuchet
MS","sans-serif";color:#666699;mso-fareast-language:EN-GB">garyclarke@m4systems.com  ceo   www.m4systems.com   +44 7710
701252</span></i></b><p class="MsoNormal"><b><i><span style="font-size:9.0pt;font-family:"Trebuchet
MS","sans-serif";color:#666699;mso-fareast-language:EN-GB"> </span></i></b><pclass="MsoNormal"><b><i><span
style="font-size:9.0pt;font-family:"Trebuchet
MS","sans-serif";color:#666699;mso-fareast-language:EN-GB"> </span></i></b><p
style="margin:0cm;margin-bottom:.0001pt"><imgalt="Description: Machine generated alternative text: ] postgres 92 b3
(192.168.221.28:5432)LIWÃIACL 
Ó Databases (3) Notice
O.O Ipostgres
e CataLogs (2)
¡‘ Ø ANSI (information_schema) row number 19 is out of range 0.18
tho PostgreSQL (pg_cataLog)
fl Casts (9)
W’ Extensions (19) [ 0K ]
Foreign Data Wrappers (0) L ____________________________
I anatiapec 151 . r" height="192" id="Picture_x0020_1" src="cid:image001.png@01CD7D1E.4E087380" width="570" /><p
style="margin:0cm;margin-bottom:.0001pt"><spanstyle="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><p
style="margin:0cm;margin-bottom:.0001pt"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#595959">Screenclipping taken: 18/08/2012
08:37</span><pstyle="margin:0cm;margin-bottom:.0001pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><pclass="MsoNormal"><b><i><span
style="font-size:9.0pt;font-family:"Trebuchet
MS","sans-serif";color:#666699;mso-fareast-language:EN-GB"> </span></i></b><pclass="MsoNormal"> </div> 

Re: pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18

From
Guillaume Lelarge
Date:
Hi,

On Sat, 2012-08-18 at 07:54 +0000, Gary Clarke (M4 Systems Ltd) wrote:
> Hello to pgadmin dev team
> (nice app by the way)
> 

Thanks.

> I noticed this pgadmin bug in beta version 2 -
> is still present in beta version 4 released yesterday.
> 
> Not critical but I thought would be worth advising you.
> 
> when I try to - object browse - pg_catalog - in any database - I get error notice - row number 19 is out of range
0..18
> 
> about 25 clicks required to get past error message - then browses ok
> 
> pg admin 1.16 beta 4  - Running on 64 bit windows
> 
> postgres v 9.2 beta 3 - running on Ubuntu 12.04 - on virtual box v1.18
> 
> postgres build has been changed - increased max for object identifiers to 256 character
> 
> NAMEDATALEN  64 to 256
> 

Are you sure you were using pgAdmin 1.16 beta 4? Because I can't
reproduce your issue, even with a NAMEDATALEN to 256 on PostgreSQL 9.2
RC 1.

If you were using pgAdmin 1.16 beta 4, then I'll need more informations
to fix the bug.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com