[BUGS] alter table
Title: Messaggio template1=#create database gesart; template1=#create user xuser; template1=# \c gesart xuser gesart=>create table a(n integer); CREATE TABLE gesart=>alter table a add column c integer references xxx(id); NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s) ALTER TABLE The table xxx doesn't exist. Is that correct or postgreSQL should report an error ? PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
[BUGS] Bug #915: problem with returning setof with double precision values
Daniel Brozek ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description problem with returning setof with double precision values Long Description I have got the table and the function (look at example code). After executing this function I have got NULL values in the place of double precision columns. But in database those values are set. Simple SELECT (select * from service) from this table works propertly - double precision columns have their proper values. I am working with 7.3.2 version of Postgresql. Sample Code CREATE FUNCTION get_krd_info (INTEGER) RETURNS SETOF service AS ' DECLARE l_service_idALIAS FOR $1; l_service service%ROWTYPE; BEGIN SELECT INTO l_service service* FROM service WHERE service.service_id = l_service_id; RETURN NEXT l_service; RETURN; END; ' LANGUAGE 'plpgsql'; No file was uploaded with this report ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] alter table
"Diego Cattelan" <[EMAIL PROTECTED]> writes: > gesart=3D>alter table a add column c integer references xxx(id); > =20 > NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s) > ALTER TABLE > =20 > The table xxx doesn't exist. > =20 > Is that correct or postgreSQL should report an error ? It is an error. 7.3.* has a bug with ALTER TABLE ADD COLUMN: any foreign-key reference clauses are ignored. This is fixed for 7.3.3. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Bug #915: problem with returning setof with double precision values
[EMAIL PROTECTED] writes: > SELECT INTO l_service service* FROM service > WHERE service.service_id = l_service_id; Shouldn't that just be SELECT INTO l_service * FROM service WHERE service.service_id = l_service_id; Or possibly SELECT INTO l_service service.* FROM service WHERE service.service_id = l_service_id; but what you wrote looks like a syntax error to me. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Bug #915: problem with returning setof with double precision
[EMAIL PROTECTED] wrote: Daniel Brozek ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description problem with returning setof with double precision values Long Description I have got the table and the function (look at example code). After executing this function I have got NULL values in the place of double precision columns. But in database those values are set. Simple SELECT (select * from service) from this table works propertly - double precision columns have their proper values. I am working with 7.3.2 version of Postgresql. Can you send a complete example? We need minimal table definition and sample data that reliably reproduces the problem. Also what OS and compiler? I'm not able to reproduce the problem here on 7.3.2 or cvs tip (see below): CREATE TABLE service( service_id int, val float8 ); insert into service values(1,1.23); insert into service values(2,2.34); CREATE OR REPLACE FUNCTION get_krd_info(INTEGER) RETURNS SETOF service AS ' DECLARE l_service_id ALIAS FOR $1; l_service service%ROWTYPE; BEGIN SELECT INTO l_service service.* FROM service WHERE service.service_id = l_service_id; RETURN NEXT l_service; RETURN; END; ' LANGUAGE 'plpgsql'; regression=# select * from get_krd_info(1); service_id | val +-- 1 | 1.23 (1 row) regression=# select * from get_krd_info(2); service_id | val +-- 2 | 2.34 (1 row) BTW, there's no reason to declare that function to return SETOF unless you loop through the results. As declared, it will never return more than one row. test=# insert into service values(1,3.45); INSERT 14266713 1 test=# select * from service; service_id | val +-- 1 | 1.23 2 | 2.34 1 | 3.45 (3 rows) test=# select * from get_krd_info(1); service_id | val +-- 1 | 1.23 (1 row) You may as well define it as: CREATE OR REPLACE FUNCTION get_krd_info(INTEGER) RETURNS service AS ' DECLARE l_service_id ALIAS FOR $1; l_service service%ROWTYPE; BEGIN SELECT INTO l_service service.* FROM service WHERE service.service_id = l_service_id; RETURN l_service; END; ' LANGUAGE 'plpgsql'; Joe ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[BUGS] Possible bug with regards to multiple persistant connections
Title: Possible bug with regards to multiple persistant connections The operating environment in which this occurred is: Apache 1.3.27 PHP 4.2.3 PostgreSQL 7.3.2 Redhat Linux 7.2 ADODB for PHP version 3.10 I have a database with an associated owner. I connect using a to this database and begin a transaction and start doing inserts and updates. However, I want to commit some other data to the same database outside of the transaction so I open a second persistant connection under the same user account and I write this information using an INSERT. In the first connection, I roll back the transaction and the insert I did under the second connection also gets rolled back. Is this supposed to occur? Perl - The programming equivalent of duct tape. Philippe Hajjar Programmer Interactive Services Group / Netensity.net http://www.isg-service.com (856) 824-9401 x33 [EMAIL PROTECTED] --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.463 / Virus Database: 262 - Release Date: 3/17/2003
[BUGS] Security problem with Postgres sql
Hi, We have a problem when logging in postgresql. We are setting the user id and password using Create User command. Now when we login the postgresql using $psql -U username databasename it does'nt prompt for the password but connects to the database. The password is correctly set and we examined the pg_shadow table also where it has been stored in the encrypted format. Please help us with this. Also when we log in the Psql with the small -u option it shows the option is deprecated , use -U option , prompts for the user id and passsword but never validates the password. If someone else has faced this problem please help us out. This is very ugently required. Regards, Deeps ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[BUGS]
Hi, I manage several databases PostgreSQL 7.3.1 and I have noticed a problem. When I delete many rows (with OID) the free space of disk doesn't changed ! I make a vacuumdb, but I doesn't notice an increase of the free space disk. In a last step, I make a backup and a restoration but, it's the same. How can I remove the OID on my disk without corrupt my databases ? I would like to upgrade in PostgreSQL 7.3.2, and I would like to know if this problem exist in this release ? Best regards. Annie. -- Faites un voeu et puis Voila ! www.voila.fr ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[BUGS] Threaded build bugs
Hello pgsql-bugs, It seems that pgsql Makefiles lack the notion of pthreads or the like libraries. I am using a threaded bind library, and when I compile postgres it fails, since it can not find some routines. Adding -lpthread to the LIBS= line in src/Makefile.global helps. I am left wondering, with a question: is omission of the library a bug, or an intended feature linked to security, stability, etc.? -- Best regards, FFKE LAN Admin mailto:[EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Security problem with Postgres sql
On Fri, Mar 21, 2003 at 16:44:07 +0530, DEEPANSHU GARG <[EMAIL PROTECTED]> wrote: > Hi, > We have a problem when logging in postgresql. > We are setting the user id and password using Create User command. > Now when we login the postgresql using > $psql -U username databasename > it does'nt prompt for the password but connects to the database. > The password is correctly set and we examined the pg_shadow table also > where it has been stored in the encrypted format. Please help us with > this. > > Also when we log in the Psql with the small -u option it shows the option > is deprecated , use -U option , prompts for the user id and passsword but > never validates the password. > > If someone else has faced this problem please help us out. This is very > ugently required. Can you show us pg_hba.conf? Most likely you are using trust as the authentication method. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Bug report
Dear Neil, > > On Thu, 2003-03-20 at 19:26, Robert E. Bruccoleri wrote: > > MIPS Pro 7.4 and MIPS Pro 7.3.1.3, 64 bit compilation model. > > I've seen some other people having troubles with PostgreSQL compiled > with Mips Pro on IRIX/MIPS -- does the problem persist if you recompile > PostgreSQL with gcc? PostgreSQL does not compile properly with gcc. I've been using PostgreSQL on Irix/MIPS for about six years -- it's quite stable. This bug appears to be related to the use of constraints in deadlock detection, it doesn't look like a compiler problem. --Bob +-++ | Robert E. Bruccoleri, Ph.D. | email: [EMAIL PROTECTED]| | President, Congenomics Inc. | URL: http://www.congen.com/~bruc | | P.O. Box 314| Phone: 609 818 7251| | Pennington, NJ 08534|| +-++ ---(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] Bug report
Dear Tom, > > > "Robert E. Bruccoleri" <[EMAIL PROTECTED]> writes: > > The PostgreSQL backend core dumps reproducibly with a set of LOCK commands that > > would normally deadlock. > > Can't duplicate that here, using either 7.3 branch or CVS tip. You sure > you have a clean build? Oh yes, the regression tests all pass, and we've been using the system heavily. What's different about this case in our shop is the heavy use of constraints. If I gave you access to an SGI running PostgreSQL 7.3.2, would you be willing to log in and explore the problem "live"? If so, I will set this up for you. Regards, Bob +-++ | Robert E. Bruccoleri, Ph.D. | email: [EMAIL PROTECTED]| | President, Congenomics Inc. | URL: http://www.congen.com/~bruc | | P.O. Box 314| Phone: 609 818 7251| | Pennington, NJ 08534|| +-++ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] Bug report
> If I gave you access to an SGI running PostgreSQL 7.3.2, would you > be willing to log in and explore the problem "live"? You bet. Do you have gdb installed? regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
