[BUGS] bug language plpgsql already exists

2010-03-16 Thread beulah prasanthi
hello I deleted existing DB and i created new DB i am getting below error how can i resolve it can any one help please language plpgsql already exists

Re: [BUGS] bug language plpgsql already exists

2010-03-16 Thread Pavel Stehule
Hello it's not bug. You registered plpgsql inside template1 database. Regards Pavel Stehule 2010/3/16 beulah prasanthi itsbeu...@gmail.com: hello I deleted existing DB and i created new DB i am getting below error how can i resolve it can any one help please language plpgsql already

Re: [BUGS] bug language plpgsql already exists

2010-03-16 Thread John R Pierce
beulah prasanthi wrote: hello I deleted existing DB and i created new DB i am getting below error how can i resolve it can any one help please language plpgsql already exists um, whats the problem? that just means someone already did the CREATE LANGUAGE plpgsql; possibly in template1 so

[BUGS] could not load library

2010-03-16 Thread beulah prasanthi
i deleted DB and created new DB when i execute my queries i got the following error.please help me could not load library C:/Program Files/PostgreSQL/8.4/lib/pldbgapi.dll: The specified module could not be found

[BUGS] update the same tuple in one command twice

2010-03-16 Thread terry
In one command, why can we update the same tuple for twice? And the result is not predicated!! Welcome to psql 8.3.3, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate

Re: [BUGS] Error when lock conflict on REPLACE function

2010-03-16 Thread Peter Eisentraut
On mån, 2010-03-15 at 14:13 -0700, Josh Berkus wrote: 1. Create a function. 2. In one session, start an explicit transaction. 3. Do a CREATE OR REPLACE on the same function, but do not commit. 4. Open a 2nd session, and an explicit transaction in that session. 5. Do a CREATE OR REPLACE on the

Re: [BUGS] update the same tuple in one command twice

2010-03-16 Thread Kevin Grittner
terry 94487...@qq.com wrote: In one command, why can we update the same tuple for twice? TEST=# update t1 set a = t2.d from t2 where a=t2.c; UPDATE 1 It says it updated it once. Why do you think otherwise? And the result is not predicated!! When you select multiple rows without

[BUGS] Facing problem with pg_dump

2010-03-16 Thread venu gopal
Hi, I have a problem with pg_dump. This command is working when I run in command prompt. pg_dump -i -h 127.0.0.1 -p 5433 -U postgres -F c -b -v -t log_term -t log_admin_m -t log_admin_s -f C:\Backup_TFGRSLog_2010-03-13131631.dat infoinfo After release my asp.net application pg_dump is not able

Re: [BUGS] update the same tuple in one command twice

2010-03-16 Thread Tom Lane
Kevin Grittner kevin.gritt...@wicourts.gov writes: terry 94487...@qq.com wrote: In one command, why can we update the same tuple for twice? TEST=# update t1 set a = t2.d from t2 where a=t2.c; UPDATE 1 It says it updated it once. Why do you think otherwise? I think maybe the OP meant to

Re: [BUGS] feature request: Loose index scans

2010-03-16 Thread Robert Haas
On Mon, Mar 15, 2010 at 3:04 PM, Gregg Lind gregg.l...@gmail.com wrote: As per http://osdir.com/ml/pgsql-hackers/2010-03/msg00331.html, I would certainly find it helpful is count(distinct(myfield)) wasn't a full index scan. We should maybe add this to our Todo file, if it's not there already

Re: [BUGS] feature request: Loose index scans

2010-03-16 Thread Tom Lane
Robert Haas robertmh...@gmail.com writes: On Mon, Mar 15, 2010 at 3:04 PM, Gregg Lind gregg.l...@gmail.com wrote: As per http://osdir.com/ml/pgsql-hackers/2010-03/msg00331.html, I would certainly find it helpful is count(distinct(myfield)) wasn't a full index scan. We should maybe add this

Re: [BUGS] Facing problem with pg_dump

2010-03-16 Thread Joshua Tolley
On Tue, Mar 16, 2010 at 10:16:36AM +0530, venu gopal wrote: Hi, I have a problem with pg_dump. This command is working when I run in command prompt. pg_dump -i -h 127.0.0.1 -p 5433 -U postgres -F c -b -v -t log_term -t log_admin_m -t log_admin_s -f

Re: [BUGS] bug or regression in plpgsql vs word window, your choice

2010-03-16 Thread David E. Wheeler
On Mar 16, 2010, at 9:20 PM, Robert Treat wrote: The problem is with the variable name window; once I changed it things worked fine. Now, Window is supposed to be a reserved word, so I am not necessarily expecting it to work any more, but this code works fine in 8.4., so I figured I