[BUGS] FW: Bug Report - PGAdmin Version 1.6.3 - Restore
_ From: Sevim Mete [mailto:[EMAIL PROTECTED] Sent: February 6, 2008 1:28 PM To: '[EMAIL PROTECTED]' Subject: Bug Report - PGAdmin Version 1.6.3 - Restore Importance: High Dear Postgres Support Team, Please see the bug report below. Could you please let me know when we can get a fix? Thanks Sevim Mete BUG REPORT: Platform: Windows XP Software: PGAdmin Version 1.6.3 Revision: 6112 Version: Postgres 8.2 PROBLEM: When restoring, Pgadmin creates duplicate data. STEPS: 1. Create a table CREATE TABLE new_table ( id integer, sub_id integer, description character(30)) ; 2. Insert 3 records INSERT INTO new_table (id, sub_id, description) VALUES (1, 2, 'test1 '); INSERT INTO new_table (id, sub_id, description) VALUES (2, 3, 'test2 '); INSERT INTO new_table (id, sub_id, description) VALUES (3, 15, 'test3 '); 3. Create a backup file 4. Create a new database 5. Restore from the backup file D:\PostgreSQLNew\8.2\bin\pg_restore.exe -i -h localhost -p 5432 -U postgres -d abc -v "E:\test2" pg_restore: connecting to database for restore pg_restore: creating SCHEMA public pg_restore: creating COMMENT SCHEMA public pg_restore: creating PROCEDURAL LANGUAGE plpgsql pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 262; 2612 16386 PROCEDURAL LANGUAGE plpgsql postgres pg_restore: [archiver (db)] could not execute query: ERROR: language "plpgsql" already exists Command was: CREATE PROCEDURAL LANGUAGE plpgsql; pg_restore: creating TABLE new_table pg_restore: restoring data for table "new_table" pg_restore: setting owner and privileges for SCHEMA public pg_restore: setting owner and privileges for COMMENT SCHEMA public pg_restore: setting owner and privileges for ACL public pg_restore: setting owner and privileges for PROCEDURAL LANGUAGE plpgsql pg_restore: setting owner and privileges for TABLE new_table WARNING: errors ignored on restore: 1 Process returned exit code 1. 6. See the message above and click on OK again D:\PostgreSQLNew\8.2\bin\pg_restore.exe -i -h localhost -p 5432 -U postgres -d abc -v "E:\test2" pg_restore: connecting to database for restore pg_restore: creating SCHEMA public pg_restore: creating COMMENT SCHEMA public pg_restore: creating PROCEDURAL LANGUAGE plpgsql pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 262; 2612 16386 PROCEDURAL LANGUAGE plpgsql postgres pg_restore: [archiver (db)] could not execute query: ERROR: language "plpgsql" already exists Command was: CREATE PROCEDURAL LANGUAGE plpgsql; pg_restore: creating TABLE new_table pg_restore: [archiver (db)] Error from TOC entry 1267; 1259 6703586 TABLE new_table postgres pg_restore: [archiver (db)] could not execute query: ERROR: relation "new_table" already exists Command was: CREATE TABLE new_table ( id integer, sub_id integer, description character(30) ); pg_restore: restoring data for table "new_table" pg_restore: setting owner and privileges for SCHEMA public pg_restore: setting owner and privileges for COMMENT SCHEMA public pg_restore: setting owner and privileges for ACL public pg_restore: setting owner and privileges for PROCEDURAL LANGUAGE plpgsql pg_restore: setting owner and privileges for TABLE new_table WARNING: errors ignored on restore: 2 Process returned exit code 1. ACTUAL RESULTS: The system restores data again and it results in duplicate records in the table. EXPECTED RESULTS: If user clicks on OK, pgAdmin Restore should not start restoring data again. REPRODUCIBLE: Yes ATTACHMENT: Please see the attached backup file. bugreport.backup Description: Binary data ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #3995: pqSocketCheck doesn't return
The following bug has been logged online: Bug reference: 3995 Logged by: Kyoko Noro Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.3 Operating system: Red Hat Enterprise Linux AS release 4 Description:pqSocketCheck doesn't return Details: Hello Support team I have a problem.May I ask your advice? Sometimes pqSocketCheck doesn't return and our appication hang.Do you have any bug report about the problem like this? ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] 8.3 problems with sspi authentication
Hello Magnus, I am using it, and it works very well for me. I've only been using it on domain attached machines though - but often using it to access the server only locally. My problem is, that the _server_ itself did not start after changing the authentication to sspi Do you have any non-microsoft software installed on the machine that could be interefering somehow. Like AV or other "security" products? Of course I have a lot of "non-microsoft software" installed on the machine :-) But I don't know how this could interfer? Avira's Antivir is installed, there's no firewall software activated, cygwin with enabled ssh server is installed, vmware workstation is installed, what else could interfer? The error you're getting is something like "function not supported", which shouldn't happen... What I miss is a more detailed log file which could tell me what exactly goes wrong (and where)... Eh, unless, you do have sspi in your pg_hba.conf, right, not gssapi? Yes I have "sspi" in my pg_hba.conf! regards, Matthias ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] BUG #3996: Reinstalling after uninstall
The following bug has been logged online: Bug reference: 3996 Logged by: James P. Yalem Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2 or 8.3 Operating system: Windows XP Description:Reinstalling after uninstall Details: When I try to reinstall 8.3 or 8.2 after uninstalling 8.2, I get an error message that the user postgres already exists and the installation program shuts down. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[BUGS] BUG: ILIKE with single-byte encoding
Hello, With PostgreSQL 8.3.0 the following bug has been introduced with the ILIKE or ~~* operator: In a database with single-byte encoding as LATIN1 the expression SELECT 'aü' ILIKE '%ü'; returns false. This error is true for every pattern, where a % is followed by a char with a decimal value between 128 and 255. I was able to track down the error to the file src/backend/utils/adt/like_match.c For the single-byte case there are some places where a (signed) char value is compared to the return value auf tolower() which is an int. The 'ü' in Latin1 is -4 as signed char and 252 as int as returned by tolower() which is obviously not equal. It could be fixed, with the appended patch. cu Rolf Jentsch Entwicklung Mitglieder-Systeme Dezentral ElectronicPartner GmbH Mündelheimer Weg 40 40472 Düsseldorf phone: +49-(0)211-4156-0 fax: +49-(0)211-4156-6865 eMail: [EMAIL PROTECTED] Sitz der Gesellschaft Düsseldorf Amtsgericht - Registergericht Düsseldorf - HRB 4078 Geschäftsführer: Oliver Haubrich, Dr. Sven-Olaf Krauß, Karl Trautman --- src/backend/utils/adt/like_match.c 2008-02-28 18:19:30.0 +0100 +++ src/backend/utils/adt/like_match.c2008-02-28 18:19:43.0 +0100 @@ -71,7 +71,7 @@ */ #ifdef MATCH_LOWER -#define TCHAR(t) tolower((t)) +#define TCHAR(t) ((char)tolower((t))) #else #define TCHAR(t) (t) #endif ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] BUG #3972: ERROR: function 59015 returned NULL
Thanks for the reply. The error was inside a personal function that called function convert with caracters that it cannot handle properly. "select proname from pg_proc where oid = 59015;" did not give me any result. I still don't know where "59015" come from, but I'm not in a hurry to find it right now :-) Thanks Maxime Le 08-02-20 à 07:19, Alvaro Herrera a écrit : Maxime Carbonneau wrote: with a database encoded with UTF8, I cannot insert into a varchar (100) column the letter œ (\u0x0153). It gives me: "ERROR: function " returned NULL" What's function 59015? Try a select proname from pg_proc where oid = 59015; -- Alvaro Herrerahttp:// www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #3995: pqSocketCheck doesn't return
"Kyoko Noro" <[EMAIL PROTECTED]> writes: > Sometimes pqSocketCheck doesn't return and our appication hang. pqSocketCheck isn't accessible from outside libpq, and furthermore it's often called with the *intention* of waiting for something to happen. You need to provide more details of what you are doing and what is happening (vs. what you expected to happen). regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
