[pgadmin-support] Bug: pgAdmin III v1.2.0 Beta 1 - wrong color processing in COMMENT

2004-09-15 Thread Alexander Kirpa
In case using "'" in comment pgAdmin display WRONG color of keywords. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[pgadmin-support] BUG: Wrong display of column properties

2005-03-26 Thread Alexander Kirpa
In property window for columns Flag 'Primary key' display value YES if column have ANY index. Best regards, Alexander Kirpa ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[pgadmin-support] BUG: Wrong Explain diagram

2005-12-24 Thread Alexander Kirpa
ore short/brief. Best regards, Alexander Kirpa ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

[pgadmin-support] pgadmin III v1.4.2 Crash on delete

2006-03-09 Thread Alexander Kirpa
ert, delete, modify) or simple populate table (cell by cell) using table browser ('View the data in the selected object.') Best regards, Alexander Kirpa ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

[pgadmin-support] Diagram 'Explain query' incorrect display of "InitPlan"

2006-03-10 Thread Alexander Kirpa
th=51) Index Cond: ("outer".nid = p_n.nid) -- Best regards, Alexander Kirpa ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

[pgadmin-support] Maintenance PK bug

2006-08-29 Thread Alexander Kirpa
27;Maintenance' 9. Select REINDEX and press 'OK' and receive 'ERROR: syntax error at or near "PRIMARY" at character 9' or see serverlog -- ERROR: syntax error at or near "PRIMARY" at character 9 STATEMENT: REINDEX PRIMARY KEY

[pgadmin-support] pgAdmin III v1.6 Beta 1 - Pg-8.2beta1: Grid editor problem

2006-10-04 Thread Alexander Kirpa
l removing (lost) definition 'int2/4/8' from 'Data Types' in, for instance, 'New Column...' b) Query tool - not useful policy in case big size of 'Output pane' after 'Restore' of window size from Maximize(full) windows size Best regards, Alexande

[pgadmin-support] Grid editor crash during row insert

2007-10-07 Thread Alexander Kirpa
PGAdmin III 1.8 Beta 5 Windows 2000 Still stable crash during insert rows in table over grid editor. For crash need sequential insert 128-130 rows without closing grid editor. Best regards, Alexander Kirpa ---(end of broadcast)--- TIP 7: You

Re: [pgadmin-support] Grid editor crash during row insert

2007-10-12 Thread Alexander Kirpa
On 8 Oct 2007, at 15:02, Dave Page wrote: > Alexander Kirpa wrote: > > PGAdmin III 1.8 Beta 5 > > Windows 2000 > > > > Still stable crash during insert rows in table over grid editor. For > > crash need sequential insert 128-130 rows without closing grid > >

Re: [pgadmin-support] Grid editor crash during row insert

2007-10-13 Thread Alexander Kirpa
x27;t understand the problem. 12345678901234567890 is out of range > for a bigint so should never be returned as one. Please provide a self > contained test case to illustrate the problem. Sorry. '12345678901234567890' should by '1234567890123456789' for sample only. I speak about partially visible (or not) field value. Crash again. Version 1.8.0 RC1 (Oct 9 2007, rev: 6725) The instruction at "0x0058b778" referenced memory at "0x031cc018". The memory could not be "read". During expanding DB tree in multi DB servers environment. Best regards, Alexander Kirpa

Re: [pgadmin-support] Grid editor crash during row insert

2007-10-15 Thread Alexander Kirpa
On 15 Oct 2007, at 9:58, Dave Page wrote: > Alexander Kirpa wrote: > > > > Crash again. > > > > Version 1.8.0 RC1 (Oct 9 2007, rev: 6725) > > The instruction at "0x0058b778" referenced memory at "0x031cc018". > > T

Re: [pgadmin-support] Grid editor crash during row insert

2007-10-18 Thread Alexander Kirpa
On 18 Oct 2007, at 12:04, Dave Page wrote: > Alexander Kirpa wrote: > In addition some suggestion about 'Types', especially 'System type'. > > Possible exist reason for 'System type' need have separate place in > > tree. In my case more 100 'S

[pgadmin-support] Refresh version string/number bug

2007-10-26 Thread Alexander Kirpa
. Connect to DB 8.3beta1 7. Try refresh DB info PgAdmin still display old 'Version string' and 'Version number' for 8.2.4 version. In addition in other situation crash: The instruction at "0x0058c438" referenced memory at "0x02e49018". The memory could

[pgadmin-support] Stable crash pgAdmin Version 1.12.0 Beta 4

2010-08-25 Thread Alexander Kirpa
) 7. Crash: 'The instructin at "0x00455f63" referenced memory at "0x0060". The memory could not be "read" '. Best regards, Alexander Kirpa -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support

[pgadmin-support] Bug report: Stable crash PgAdmin III 1.18 (Sep 10 2013, Rev: REL-1_18_0)

2013-09-17 Thread Alexander Kirpa
Click on OK to terminate the application. Workaround: Uninstall version 1.18.0 and install version 1.16.1 (Dec 4 2012, rev: REL-1_16_1) - no crash Best regards, Alexander Kirpa -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: ht

[pgadmin-support] pgAdmin III v1.22.0 - installation at Windows XP

2016-01-24 Thread Alexander Kirpa
/downloads/en/details.aspx?FamilyID=5a58b56f-60 b6-4412-95b9-54d056d6f9f4&displaylang=en pgAdmin III v1.22.0, after installing this hot-fix, installed at Windows XP and work w/o problem. Best regards, Alexander Kirpa -- Sent via pgadmin-support mailing list (pgadmin-support@postgresq