Thread: bug in Pgadmin 1.0.1

Hi
There is bug in Pgadmin 1.0.1 .  When problems starts, Pgadmin suddenly
shut down every time I try to insert my samples ( 6 samples are attached
to this letter) . This is true only for databases in KOI8 encoding (for
database in unicode  encoding  all this problems absent, all works
right). To reproduce the problem you should do next :
In console:
CREATE DATABASE my_testdb   WITH ENCODING = 'KOI8';
Then you should apply my little dump (my_dump is attached to this letter).
In Pgadmin:
Insert my 6 samples into pressa.monitoring (into , for example, tema -
in russian)
Then delete all 6 samples and then insert again , and then problems
start ...
I think this bug concern somehow with "Vacuum" (sometimes Vacuum helps
for short time).
Operation system: win XP, distribution binary, database Postgresql 7.4 RC1.

------------------------------------------------------------------------------------------------------------------------------


There is question.
CREATE VIEW my_view AS SELECT * from my_table;
CREATE RULE my_rule AS ON INSERT TO my_view DO INSTEAD INSERT INTO
my_table ...
I can nothing insert into my_view, using Pgadmin or even Phppgadmin. But
I can insert rows into my_view only working in console ... Is it right
behavior?

---------------------------------------------------------------------------------------------------------------------------------

Alexandr S wrote:

> Hi
> There is bug in Pgadmin 1.0.1 .  When problems starts, Pgadmin 
> suddenly shut down every time I try to insert my samples ( 6 samples 
> are attached to this letter) . This is true only for databases in KOI8 
> encoding (for database in unicode  encoding  all this problems absent, 
> all works right). To reproduce the problem you should do next :
> ...
> Then delete all 6 samples and then insert again , and then problems 
> start ...
> I think this bug concern somehow with "Vacuum" (sometimes Vacuum helps 
> for short time).
> Operation system: win XP, distribution binary, database Postgresql 7.4 
> RC1.


I'm not sure what you mean with "insert again", do you mean pg_restore?

We just located a very nasty bug regarding backend notice handling in 
threads, so this might be the reason why your problem is dependend on db 
encoding or vacuum. Please try V1.0.2 (might take another day until it's 
replicated everywhere), whether the problem persists. If it does, please 
tell us.

Regards,
Andreas