[BUGS] BUG #1485: upper case user names / creatuser
The following bug has been logged online: Bug reference: 1485 Logged by: Hannes Erven Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.7 Operating system: 2.6.10-gentoo-r6 Description:upper case user names / creatuser Details: I tried creating a new user the way mentioned in the Docs, but (postgres owning user removed from the output): $ createuser Enter name of user to add: Hannes Shall the new user be allowed to create databases? (y/n) n Shall the new user be allowed to create more new users? (y/n) n CREATE USER $ psql template1 Welcome to psql 7.4.7, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit template1=# alter user Hannes password '***'; ERROR: user "hannes" does not exist template1=# select * from pg_catalog.pg_user usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | valuntil | useconfig --+--+-+--+---+--+-- +--- Hannes | 100 | f | f| f | | | (2 rows) I then created another user, 'hannes', with createuser, and then I was able to alter the passwords, altough I now had two users in pg_user: hannes and Hannes. template1=# drop user Hannes ; DROP USER template1=# select * from pg_user ; Hannes | 100 | f | f| f | | | template1=# drop user Hannes ; ERROR: user "hannes" does not exist I had expected either createuser create a 'hannes' or the alter/drop user commands to respect case in user names. with best regards, -hannes ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] BUG #1487: Index problem
The following bug has been logged online: Bug reference: 1487 Logged by: Tom Yeh Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Windows XP Description:Index problem Details: I created an index for a table, say Entity, on a field, say id. Then, the follwoing two SQL has different result: select * from "Entity" e where e.id = '1000' and select * from "Entity" e where e.id like '1000' (The later uses sequential scan. BTW, while 7.4.x uses index why 8.0 behave worse?) Once I re-index it, the problem is gone. However, the problem comes back randomly if I change some id. The above can be replicated by using pgAdmin III only. ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] diff value retuns, debug mode and play mode
I have a postgresql function at the bottom , when i run at EMS POSTGRESQL debug mode with F8 step by step. Its work great but when i use with play button it returns null what is the different about debug mode and run mode. BEST REGARDS. CREATE OR REPLACE FUNCTION "public"."allocatedamount" (varchar, integer) RETURNS numeric AS $body$ /* allocatedamount (varchar,integer) raporlarda kullan?lmak ?zere belirli bir sold un nekadar?n?n allocate edildi?ini bulmak i?in $1: Varchar: Tablo ismi.(SOCIAL,ACCOMODATION,vs) $2: Integer: Soldid. */ declare res numeric(15,2); _pida integer[4]; _pid integer; _rec record; begin if $1 = 'REGISTRATION' then begin _pid:=1; for _rec in select personaldetails.id from personaldetails where personaldetails.id=$2 or personaldetails.masterid=$2 loop _pida[_pid]:=_rec.id; _pid:=_pid+1; end loop; select into res sum(allocatedpayments.amount) from allocatedpayments where allocatedpayments.tablename='REGISTRATION' and allocatedpayments.tableid = ANY (_pida::integer[]); res=888; end; ELSIF $1 = 'MASTER-REGISTRATION' then select into res sum(allocatedpayments.amount) from allocatedpayments where allocatedpayments.tablename='REGISTRATION' and allocatedpayments.tableid=$2; ELSIF $1 = 'ACC-REGISTRATION' then select into res sum(allocatedpayments.amount) from allocatedpayments where allocatedpayments.tablename='REGISTRATION' and allocatedpayments.tableid=$2; else select into res sum(allocatedpayments.amount) from allocatedpayments where allocatedpayments.tablename=$1 and allocatedpayments.tableid=$2; end if; if res is null then res:=0; end if; return res; end; $body$ LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY INVOKER; ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[BUGS] BUG #1488: CREATE TABLESPACE does not work
The following bug has been logged online: Bug reference: 1488 Logged by: Jesper Udby Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Win32 XP Pro SP2 Description:CREATE TABLESPACE does not work Details: Hello. Trying to create a tablespace fails with msg "ERROR: could not set permissions on directory "...": Permission denied". E.g. CREATE TABLESPACE pgtest LOCATION 'c:\\pgtest'; (Directory c:\\pgtest exists and is readable etc.) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] BUG #1486: Apostrophes are not ignored in pgplsql comments
The following bug has been logged online: Bug reference: 1486 Logged by: Andrew Gold Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.7 Operating system: Debian Linux Description:Apostrophes are not ignored in pgplsql comments Details: In pgplsql functions, apostrophes in comments are not ignored by the pgplsql interpreter. Parsing errors result from correct spelling in comments. For example, a comment such as: -- This can't be a good way to solve this. will generate errors. This seems to be a general bug and was easily duplicated. Thanks, Andrew Gold ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[BUGS] problem installing postgresql-8.0.1 on Windows 2K
It gives a non-descriptive error message "Installation ended prematurely because of an error". It is repeatable. The end of the log file is the following: Property(C): OriginalDatabase = C:\tmp\postgresql-8.0.1\postgresql-8.0-int.msi Property(C): SOURCEDIR = C:\tmp\postgresql-8.0.1\ Property(C): VersionHandler = 2.00 Property(C): UILevel = 5 Property(C): ACTION = "" Property(C): EXECUTEACTION = INSTALL Property(C): ROOTDRIVE = C:\ Property(C): CostingComplete = 1 Property(C): OutOfDiskSpace = 0 Property(C): OutOfNoRbDiskSpace = 0 Property(C): PrimaryVolumeSpaceAvailable = 0 Property(C): PrimaryVolumeSpaceRequired = 0 Property(C): PrimaryVolumeSpaceRemaining = 0 Property(C): INSTALLLEVEL = 1 === Logging stopped: 2/20/2005 07:57:46 === MSI (c) (64:E0): Note: 1: 1708 MSI (c) (64:E0): Note: 1: 2205 2: 3: Error MSI (c) (64:E0): Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 MSI (c) (64:E0): Note: 1: 2205 2: 3: Error MSI (c) (64:E0): Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (64:E0): Product: PostgreSQL 8.0 -- Installation failed. MSI (c) (64:E0): Grabbed execution mutex. MSI (c) (64:E0): Cleaning up uninstalled install packages, if any exist MSI (c) (64:E0): MainEngineThread is returning 1603 === Verbose logging stopped: 2/20/2005 07:57:46 === Any ideas? Best regards, Juu. __ Advertisement: Atrodiet savu celojumu seit!
[BUGS] BUG #1489: configure confusion
The following bug has been logged online: Bug reference: 1489 Logged by: rob delong Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: RH 9 Description:configure confusion Details: Not really a bug, but it confused me for a bit. Thought you might want to know. On RH 9, configure using --with-openssl failed with ssl.h not found or useable even though it was there. Turns out openssl as installed by the RH installation is compiled with kerberos support. ssl.h includes kssl.h which includes krb5.h. The last is stuffed into /usr/kerberos/include if you let the RH installer do its thing. Configure does not check /usr/kerberos/include for headers unless you tell it. If you add --with-includes=/usr/kerberos/include configure is happy. BTW messages from configure were misleading, looked like it couldn't find ssl.h, but inspection of config.log showed the actual error. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG #1492: PostgreSQL ODBC error
The following bug has been logged online: Bug reference: 1492 Logged by: Rong Wang Email address: [EMAIL PROTECTED] PostgreSQL version: 8 Operating system: Windows 2003 Description:PostgreSQL ODBC error Details: ODBC having an open nature allows client application to query SQL Syntax capabilities of the database. The ODBC CK (an aplication using ODBC)uses this to make sure it generates the correct syntax. When creating indexes it asks the database if schema names should be used. PostgreSQL indicates they should be used. When we do this we get a syntax error. The technical detail: When calling SQLGetInfo with the SQL_SCHEMA_USAGE InfoType it returns a value with the SQL_SU_INDEX_DEFINITION set. It looks like this should not be set. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] BUG #1490: contrib .sql.in sed command bogus
The following bug has been logged online: Bug reference: 1490 Logged by: Alexis Wilke Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Linux Description:contrib .sql.in sed command bogus Details: Inside pgxs.mk I had to change the $$libdir into $(libdir ) to get the proper path in the final .sql file: ifneq (,$(MODULES)$(MODULE_big)) %.sql: %.sql.in sed 's,MODULE_PATHNAME,$(libdir)/$*,g' $< >$@ endif ---(end of broadcast)--- TIP 3: 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 #1484: client gets the wrong character set
The following bug has been logged online: Bug reference: 1484 Logged by: Johann Gregorich Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.0 Operating system: Linux and Windows XP Description:client gets the wrong character set Details: Hi, when connecting from Win XP (german) to pg 8.0.0 (unicode database on suse linux 9.2) via ODBC we do not get as expected Latin9 charcter set from the backend, but UTF8. This results in a odbc message 'wrong unicode character...' We tried a workaround to set the client character set after every cursor connect (before executing the statement), but no chance. Has somebody an idea how to overcome this mess? Regards Hans ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG #1491: Getting an "undefined symbol" when loading contrib mod.
The following bug has been logged online:
Bug reference: 1491
Logged by: Alexis Wilke
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux
Description:Getting an "undefined symbol" when loading contrib mod.
Details:
I'm trying to use ltree to sort one of my table using a tree like column
("1", "1.1", "1.2", "2", "2.1", etc.)
Everything compiles, after my fix to the .sql.in -> .sql convertion
($(libdir) instead of $$libdir in pgxs.mk) and everything also seems to be
installed properly.
However, in version 7.4.6 and version 8.0.1, when I try to load the module,
it says it can't find the symbol errstart (one of the elog functions better
known as ereport).
There are a few versions if that helps at all...
gcc (GCC) 3.4.3
GNU ld version 2.13.90.0.18 20030206
ldd (GNU libc) 2.3.2
There is the complete message I'm getting from postgres
crm=> SET search_path = public;
SET
crm=> CREATE FUNCTION ltree_in(cstring)
crm-> RETURNS ltree
crm-> AS '/usr/local/pgsql/lib/ltree'
crm-> LANGUAGE 'C' WITH (isstrict);
NOTICE: ProcedureCreate: type ltree is not yet defined
ERROR: Load of file /usr/local/pgsql/lib/ltree.so failed:
/usr/local/pgsql/lib/ltree.so: undefined symbol: errstart
---(end of broadcast)---
TIP 3: 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] [ADMIN] Postgres crashed on invalid IP entry in pg_hba.conf
Pallav Kalva wrote: > I am using 7.4.2 on Redhat 9 Linux 2.4. I know iam on old version, we > are actually planning to move to 8.0.1 soon, I just wanted to know if > this is bug if so if it is 7.4.2 related . You just need to stop your server, install 7.4.7 and restart. There is no reason to be running 7.4.2 unless you can't do 2 minutes of downtime. Even if you upgrade to 8.0.1 you will need to do this when 8.0.2 comes out. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
