Re: [BUGS] BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"

[Dave Page]

On Wed, Dec 29, 2010 at 7:09 PM, Gabe Nell  wrote:
>
> Launching psql fails:
>
> ubu...@host:~$ /opt/PostgreSQL/9.0/bin/psql -Upostgres
> Password for user postgres:
> psql (9.0.2)
> Type "help" for help.
>
> Cannot read termcap database;
> using dumb terminal settings.
> Aborted
> ubu...@host:~$
>
> The above works fine with 9.0.1, suggesting this is a new issue in 9.0.2. I
> tried both 32bit and 64bit, same problem. Interestingly, the problem doesn't
> repro under byobu (Ubuntu's enhanced 'screen' utility).

There was a change in 9.0.2 to use libedit instead of readline for
this (readline is GPL, which is not acceptable to some people who wish
to use Postgres in other products). One of my colleagues has tested
the issue reported and confirmed that installing the OS's termcap
package should solve the problem.


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] Re: to_timestamp returns the incorrect result for the DST fall over time.

[Gouse]

I am afraid this may not give the result I am looking for. The  sp x(text)
gives me the result always will be UTC time zone.
My requirement here is, that i should pass the UTC time in text as a
parameter and should return local timestamp with timzone for that UTC time.


select x('2010-03-28 01:00:03 243') should return '2010-03-28 02:00:03.243 +
01' as locks are supposed to jump from 1AM directly to 2AM when my clock is
set to GMT 

select x ('2010-03-28 02:00:03 243') should return '2010-03-28 03:00:03.243
+ 01' 
select x ('2010-03-28 03:00:03 243') should return '2010-03-28 04:00:03.243
+ 01' 

Thanx,
Gouse


-- 
View this message in context: 
http://postgresql.1045698.n5.nabble.com/to-timestamp-returns-the-incorrect-result-for-the-DST-fall-over-time-tp3327393p3330384.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] Re: to_timestamp returns the incorrect result for the DST fall over time.

[Kevin Grittner]

Gouse  wrote:
 
> I am afraid this may not give the result I am looking for.
 
It sounds like you didn't even try it.  That's bad form.
 
I'm wondering why you bring to_timestamp into it at all, though. 
Are you aware of the behavior of casting?:
 
test=# select '2011-01-15 00:00:00.0 UTC'::timestamptz;
  timestamptz

 2011-01-14 18:00:00-06
(1 row)
 
If you put together a string with the UTC timezone specified, and
cast it to timestamptz, I think you'll get what you want.
 
-Kevin

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5641: Can not create any python language

[areveille]

Hi,

I'm facing the same issue in the same environment and the solution given by
Ashesh Vashi is not working. :(
Once I have copied plpython.dll as plpython3.dll, I still can't create the
language plpython3u for a database.

Is there another work around?

Thanks,

Alban.
-- 
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330444.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5641: Can not create any python language

[Ashesh Vashi]

Hi Alban,

Can you please open the plpython.dll (now, plpython3.dll) in the dependency
walker and check if it satisfies all the required dlls?
You can find the dependency walker @ dependencywalker.com.

--
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company



*http://www.linkedin.com/in/asheshvashi*


On Thu, Jan 6, 2011 at 7:38 PM, areveille  wrote:

>
> Hi,
>
> I'm facing the same issue in the same environment and the solution given by
> Ashesh Vashi is not working. :(
> Once I have copied plpython.dll as plpython3.dll, I still can't create the
> language plpython3u for a database.
>
> Is there another work around?
>
> Thanks,
>
> Alban.
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330444.html
> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

Re: [BUGS] BUG #5641: Can not create any python language

[Robert Haas]

On Thu, Jan 6, 2011 at 9:08 AM, areveille  wrote:
> I'm facing the same issue in the same environment and the solution given by
> Ashesh Vashi is not working. :(
> Once I have copied plpython.dll as plpython3.dll, I still can't create the
> language plpython3u for a database.

I guess the obvious question is - what happens when you try it?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5641: Can not create any python language

[Ashesh Vashi]

It shows you all the dependent dlls (present or missing) in it.
It also shows the exported functions by that particular dll.

That gives you idea, if something is wrong with your environment or some
dlls are missing.

You can check more details on http://dependencywalker.com/
(NOTE: bottom of the page of this link shows you the screen-shot of
dependency walker.)

--
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company



*http://www.linkedin.com/in/asheshvashi*


On Thu, Jan 6, 2011 at 8:07 PM, Robert Haas  wrote:

> On Thu, Jan 6, 2011 at 9:08 AM, areveille  wrote:
> > I'm facing the same issue in the same environment and the solution given
> by
> > Ashesh Vashi is not working. :(
> > Once I have copied plpython.dll as plpython3.dll, I still can't create
> the
> > language plpython3u for a database.
>
> I guess the obvious question is - what happens when you try it?
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

Re: [BUGS] BUG #5641: Can not create any python language

[areveille]

Hi,

I used dependency walker in order to see which dependencies could be
unsatified in plpython.dll and indeed some of them were missing : 
- python26.dll (I had python2.7 installed but obviously it requires 2.6.)
- some .dll that are in the bin folder of posgreSQL

So I installed python 2.6 and copy/paste the other missing dlls

In the end, when I use dependency walker,  plpython.dll still have a warning
: 
"Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module."
Here is a screen shot of the result in dependency walker : 
http://postgresql.1045698.n5.nabble.com/file/n3330551/depWalker.png
depWalker.png 

I still can't create the language.
 
Thanks,

Alban.
-- 
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330551.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5641: Can not create any python language

[areveille]

The result is still the same (means "ERREUR:  n'a pas pu charger la
bibliothèque « C:/Program Files/PostgreSQL/9.0/lib/plpython3.dll » : unknown
error 126" = Can't load  C:/Program Files/PostgreSQL/9.0/lib/plpython3.dll
-- 
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330556.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5641: Can not create any python language

[Ashesh Vashi]

And, make sure you create the plpythonu language not plpython3u.

--
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company



*http://www.linkedin.com/in/asheshvashi*


On Thu, Jan 6, 2011 at 8:46 PM, Ashesh Vashi
wrote:

> This warning will be there for any dlls.
> So - you can ignore them.
>
> If you have renamed the plpython.dll to plpython3.dll, then please revert
> it back to original one.
> And, then try to create the language.
>
>
>  --
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
>
>
>
> *http://www.linkedin.com/in/asheshvashi*
>
>
> On Thu, Jan 6, 2011 at 8:42 PM, areveille  wrote:
>
>>
>> Hi,
>>
>> I used dependency walker in order to see which dependencies could be
>> unsatified in plpython.dll and indeed some of them were missing :
>> - python26.dll (I had python2.7 installed but obviously it requires 2.6.)
>> - some .dll that are in the bin folder of posgreSQL
>>
>> So I installed python 2.6 and copy/paste the other missing dlls
>>
>> In the end, when I use dependency walker,  plpython.dll still have a
>> warning
>> :
>> "Warning: At least one module has an unresolved import due to a missing
>> export function in a delay-load dependent module."
>> Here is a screen shot of the result in dependency walker :
>> http://postgresql.1045698.n5.nabble.com/file/n3330551/depWalker.png
>> depWalker.png
>>
>> I still can't create the language.
>>
>> Thanks,
>>
>> Alban.
>> --
>> View this message in context:
>> http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330551.html
>> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>>
>> --
>> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-bugs
>>
>
>

Re: [BUGS] BUG #5641: Can not create any python language

[Ashesh Vashi]

This warning will be there for any dlls.
So - you can ignore them.

If you have renamed the plpython.dll to plpython3.dll, then please revert it
back to original one.
And, then try to create the language.

 --
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company



*http://www.linkedin.com/in/asheshvashi*


On Thu, Jan 6, 2011 at 8:42 PM, areveille  wrote:

>
> Hi,
>
> I used dependency walker in order to see which dependencies could be
> unsatified in plpython.dll and indeed some of them were missing :
> - python26.dll (I had python2.7 installed but obviously it requires 2.6.)
> - some .dll that are in the bin folder of posgreSQL
>
> So I installed python 2.6 and copy/paste the other missing dlls
>
> In the end, when I use dependency walker,  plpython.dll still have a
> warning
> :
> "Warning: At least one module has an unresolved import due to a missing
> export function in a delay-load dependent module."
> Here is a screen shot of the result in dependency walker :
> http://postgresql.1045698.n5.nabble.com/file/n3330551/depWalker.png
> depWalker.png
>
> I still can't create the language.
>
> Thanks,
>
> Alban.
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330551.html
> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

Re: [BUGS] BUG #5641: Can not create any python language

[areveille]

In fact I always had plpython.dll since I duplicated the file (one named
plpython.dll and the other plpython3.dll).

Anyways, now I have deleted plpython3.dll (so I just have plpython.dll) and
"create language plpython;" answers : ERREUR:  n'a pas pu charger la
bibliothèque « C:/Program Files/PostgreSQL/9.0/lib/plpython.dll » : unknown
error 126 which means "can't load C:/Program
Files/PostgreSQL/9.0/lib/plpython.dll"

Thanks for your time,

Alban.
-- 
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330575.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5641: Can not create any python language

[Ashesh Vashi]

Are the python binaries in your system level PATH environment?
If not, you need to make sure the bin folder of python should be in your
system level PATH variable.
Check this link for the reference:
http://geekswithblogs.net/renso/archive/2009/10/21/how-to-set-the-windows-path-in-windows-7.aspx

Then - you need to restart your postgres service.

--
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company



*http://www.linkedin.com/in/asheshvashi*


On Thu, Jan 6, 2011 at 8:53 PM, areveille  wrote:

>
> In fact I always had plpython.dll since I duplicated the file (one named
> plpython.dll and the other plpython3.dll).
>
> Anyways, now I have deleted plpython3.dll (so I just have plpython.dll) and
> "create language plpython;" answers : ERREUR:  n'a pas pu charger la
> bibliothèque « C:/Program Files/PostgreSQL/9.0/lib/plpython.dll » : unknown
> error 126 which means "can't load C:/Program
> Files/PostgreSQL/9.0/lib/plpython.dll"
>
> Thanks for your time,
>
> Alban.
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330575.html
> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

Re: [BUGS] BUG #5641: Can not create any python language

[areveille]

This was the final step : it worked out.

Thanks for your time, your understandable explanations!

Alban,
-- 
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330632.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5809: bigserial duplicate value

[Melzaiady]

 i relying on PostgreSQL to supply a default value,
i  have application at  hospital and application appear error about duplicate 
value. 

There was a primary key on this columns but i found error form my application 
about duplicate value and can`t insert value then i remove the primary key 
constraint to try  to find problem and try again i found bigserial  put 
duplicate value on fields .
 



Mahmoud El Zaiady
Bachelor of Information Systems
Faculty of Computers & Information Sciences
Mansoura University
 
 






From: Joshua Tolley 
To: Jeff Davis 
Cc: mahmoud elzaiady ; pgsql-bugs@postgresql.org
Sent: Tue, January 4, 2011 6:34:57 PM
Subject: Re: [BUGS] BUG #5809: bigserial duplicate value

On Mon, Jan 03, 2011 at 11:04:17AM -0800, Jeff Davis wrote:
> On Sun, 2011-01-02 at 11:40 +, mahmoud elzaiady wrote:
> > i ask ,bigserial must not duplicate the value ?
> > how solve this problem
> 
> This is probably due to the sequence being reset somehow. Have you
> dumped/reloaded recently? Did you manually back up or copy the table?

Alternatively, perhaps at some point you've added data to that column, rather
than relying on PostgreSQL to supply a default value.

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com



  

[BUGS] BUG #5813: Cross Database Access in the same server using DBlink

[Peevee]

The following bug has been logged online:

Bug reference:  5813
Logged by:  Peevee
Email address:  peeve...@yahoo.com
PostgreSQL version: 9.0.2
Operating system:   Windows 7
Description:Cross Database Access in the same server using DBlink
Details: 

I have created a table named "TestTableA" in a Database named "DatabaseA"
and created again another table named "TestTableB" in "DatabaseB".

CREATE TABLE "TestTableA"
(
  "Name" character varying(50)[],
  "TableId" serial NOT NULL,
  CONSTRAINT "pk_tableID" PRIMARY KEY ("TableId")
)
WITH (
  OIDS=FALSE
);
ALTER TABLE "TestTableA" OWNER TO postgres;

CREATE TABLE "TestTableB"
(
  "TableId" serial NOT NULL,
  "Name" character varying(50)[],
  CONSTRAINT "pk_tableID" PRIMARY KEY ("TableId")
)
WITH (
  OIDS=FALSE
);
ALTER TABLE "TestTableB" OWNER TO postgres;


Now I'm trying to access "TableB" which is located in "DatabaseB" from my
function located in "DatabaseA".

create or replace function TestFunction(pInput character varying) RETURNS
VOID as
$$
DECLARE 

rec record;
BEGIN

SELECT * from dblink('dbname=DMATempLog port=5432 user=postgres
password=somepassword','Select TableName from TestTableB LIMIT 1' )as
rec(tablename character varying(50));
END;
$$ language plpgsql;

and this generates an error:

ERROR:  relation "testtableb" does not exist
CONTEXT:  Error occurred on dblink connection named "unnamed": could not
execute query.
SQL statement "SELECT * from dblink('dbname=DMATempLog port=5433
user=postgres password=Pv12062010igen','Select TableName from testtableb
LIMIT 1' )as rec(tablename character varying(50))"
PL/pgSQL function "testfunction" line 12 at SQL statement

** Error **

ERROR: relation "testtableb" does not exist
SQL state: 42P01
Context: Error occurred on dblink connection named "unnamed": could not
execute query.
SQL statement "SELECT * from dblink('dbname=DMATempLog port=5433
user=postgres password=Pv12062010igen','Select TableName from testtableb
LIMIT 1' )as rec(tablename character varying(50))"
PL/pgSQL function "testfunction" line 12 at SQL statement

I'm solving this problem for almost 1 week..could you please help me..i read
a lot about dblink and try all their suggestions but none of them works.Am i
missing something here?

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] certification courses for postgreSQL......

[harshad]

 dear sir/madam,

 i m the beginner of postgreSQL database.and want to become expert in this 
database.

is theer any certification courses for postgreSQL database available?

kindly guide me .


thanx in anticipation
regards 
harshad

हर्षद वाजार

[BUGS] BUG #5814: documentation bug

[Antje Petersen]

The following bug has been logged online:

Bug reference:  5814
Logged by:  Antje Petersen
Email address:  antje.peter...@desy.de
PostgreSQL version: 8.1.21
Operating system:   Scientific Linux 5
Description:documentation bug
Details: 

According to the documentation
createuser --no-superuser and 
createuser --no-createrole is the default.
This is not true. The default is to be asked
Shall the new role be a superuser? (y/n) 
Shall the new role be allowed to create more new roles? (y/n) 

Cheers, 

antje

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #5815: connecting to Atllassian products

[kapil]

The following bug has been logged online:

Bug reference:  5815
Logged by:  kapil
Email address:  kapil_bo...@yahoo.com
PostgreSQL version: 8.4
Operating system:   windows
Description:connecting to Atllassian products
Details: 

hello
I have connected postgreSql with  Atllassian products.
i receiving the follwing error.::
 java.sql.SQLException: Connections could not be acquired from the
underlying database.



So please help me out
Thanks in advance

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #5816: index not used in function

[frank]

The following bug has been logged online:

Bug reference:  5816
Logged by:  frank
Email address:  fr...@ros-i.com
PostgreSQL version: 8.3.7
Operating system:   linux
Description:index not used in function
Details: 

Linux: Linux  2.6.24-24-server #1 SMP Tue Jul 7 20:21:17 UTC
2009 i686 GNU/Linux

Postgres: "PostgreSQL 8.3.7 on i486-pc-linux-gnu, compiled by GCC cc (GCC)
4.2.4 (Ubuntu 4.2.4-1ubuntu3)"

Table Description:
1. table (say thisTable) with a column (say thisColumn) of varchar in mixed
case data
2. w/o primary key on this column
3. an upper case index on this column with text_pattern_ops as the opclass

Query Description:
1. select "thisColumn" from "thisTable" where upper("thisColumn") like
'ABC%'
2. select * from get_this_column('ABC')
where get_this_column() is defined as:

CREATE OR REPLACE FUNCTION get_this_column(c text)
  RETURNS SETOF text AS
$BODY$  
   SELECT "thisColumn" FROM "thisTable" WHERE upper("thisColumn") like $1
limit 10;  
$BODY$
  LANGUAGE 'sql' VOLATILE
  COST 100
  ROWS 1000;
ALTER FUNCTION get_this_column(text) OWNER TO postgres;

Issue Description:
The plain query (1) uses the upper case index.
The function (2), even though having the same underlying query, does not
seem to be able to use index. The wild card can either be in the argument or
appended at the query inside the function, the result is the same.

Further Question:
Why can't force the use of index (even if the plan results in worse
performance when user desires)?
The index HINT (of ORACLE say) is a bad concept and a horrible design idea.
The user should be allowed to force the use of any index regardless of
performance. Anyway, the user should know what he/she is doing. Besides, an
explain could show which, the system plan or the user's, is better.

The combination described here is perhaps not normal. I have not tested it
with any other version. Likely the same is true for all versions including
9.

Regardless of resolution, I would appreciate a brief response.

Thanks

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #5817: Language problem...

The following bug has been logged online:

Bug reference:  5817
Logged by:  
Email address:  jeng...@hotmail.com
PostgreSQL version: any, so far
Operating system:   Windows 7
Description:Language problem...
Details: 

I use a W7 english operating system, with Norwegian input (keyboard etc).

Every version of postgres I have tried to install has stopped on the fact
that it does not recognize "Norsk bokmål" as system locale. (It seems to
stop on the letter "å" in "bokmål")

No big issue, as all I have to do is change the system locale to English,
but it should also be an easy problem to fix(?). (To me it seems the
installer is trying to READ the systems locale instead of just use it from
MY machine. When it does not recognize it, everything stops)

And I have tried installing postres from the newest version to 8,3 without
success (before changing to english)

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5813: Cross Database Access in the same server using DBlink

[Kevin Grittner]

"Peevee"  wrote:
 
> Select TableName from TestTableB LIMIT 1
 
> ERROR:  relation "testtableb" does not exist
 
Identifiers containing uppercase letters must be quoted.
 
-Kevin

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS]certification courses for postgreSQL......

[Kevin Grittner]

"harshad"  wrote:
 
> i m the beginner of postgreSQL database.and want to become expert
> in this database.
> 
> is theer any certification courses for postgreSQL database
> available?
 
Welcome to the world of PostgreSQL!  However, this is clearly not a
bug report, so it doesn't belong on the bugs list.  Review the
available lists and pick one that fits better -- perhaps
pgsql-novice:
 
http://www.postgresql.org/community/lists/
 
-Kevin

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5817: Language problem...

[Dave Page]

On Wed, Jan 5, 2011 at 10:02 PM,   wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5817
> Logged by:
> Email address:      jeng...@hotmail.com
> PostgreSQL version: any, so far
> Operating system:   Windows 7
> Description:        Language problem...
> Details:
>
> I use a W7 english operating system, with Norwegian input (keyboard etc).
>
> Every version of postgres I have tried to install has stopped on the fact
> that it does not recognize "Norsk bokmål" as system locale. (It seems to
> stop on the letter "å" in "bokmål")
>
> No big issue, as all I have to do is change the system locale to English,
> but it should also be an easy problem to fix(?). (To me it seems the
> installer is trying to READ the systems locale instead of just use it from
> MY machine. When it does not recognize it, everything stops)
>
> And I have tried installing postres from the newest version to 8,3 without
> success (before changing to english)

The installer builds a list of available locales by using a Windows
API to query the system. It then populates the combo box, and adds a
"Default locale" option to the list, which if selected, means that the
installer will leave initdb to choose the locale based on the
environment.

It's not clear from your report if the list is not populated
correctly, or if default option fails. Can you provide the installer
log from %TEMP%?


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5815: connecting to Atllassian products

[Kevin Grittner]

"kapil"  wrote:
 
> I have connected postgreSql with  Atllassian products.
> i receiving the follwing error.::
>  java.sql.SQLException: Connections could not be acquired from
>  the underlying database.
 
This doesn't sound like a bug, at least not a PostgreSQL bug.  You
might do better to as whoever supplies Atllassian products (whatever
those are).  Regardless of where you report it, you will probably
need to supply more information.  See this page for ideas on what to
include:
 
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
 
-Kevin

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5816: index not used in function

[Kevin Grittner]

"frank"  wrote:
 
> WHERE upper("thisColumn") like $1
 
The function's plan is kept from one execution to another, and it
can't know what will be in the first parameter -- perhaps '%X%'?  If
you build up the statement in a string and EXECUTE it, you might get
the desired behavior.
 
Anyway, next time you have an issue like this, please post to the
performance list; this is not a bug.
 
-Kevin

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"

[Gabe Nell]

> There was a change in 9.0.2 to use libedit instead of readline for
> this (readline is GPL, which is not acceptable to some people who wish
> to use Postgres in other products). One of my colleagues has tested
> the issue reported and confirmed that installing the OS's termcap
> package should solve the problem.

Ubuntu doesn't seem to use termcap, an apt-cache search for termcap
turns up nothing relevant. I did some searching and the closest
suggestion I could find was to install libncurses5-dev, but this
didn't help. Can you suggest that the appropriate package to install
on Ubuntu?

Thanks!

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"

[Dave Page]

On Thu, Jan 6, 2011 at 8:54 PM, Gabe Nell  wrote:
>> There was a change in 9.0.2 to use libedit instead of readline for
>> this (readline is GPL, which is not acceptable to some people who wish
>> to use Postgres in other products). One of my colleagues has tested
>> the issue reported and confirmed that installing the OS's termcap
>> package should solve the problem.
>
> Ubuntu doesn't seem to use termcap, an apt-cache search for termcap
> turns up nothing relevant. I did some searching and the closest
> suggestion I could find was to install libncurses5-dev, but this
> didn't help. Can you suggest that the appropriate package to install
> on Ubuntu?

Hmm, good question. Let me ask my colleague and get back to you.


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5809: bigserial duplicate value

[Robert Haas]

On Wed, Jan 5, 2011 at 12:38 AM, Melzaiady  wrote:
>  i relying on PostgreSQL to supply a default value,
> i  have application at  hospital and application appear error about
> duplicate value.
> There was a primary key on this columns but i found error form my
> application about duplicate value and can`t insert value then i remove the
> primary key constraint to try  to find problem and try again i found
> bigserial  put duplicate value on fields .

I'm pretty sure there isn't a bug that's making the sequence return
duplicate values, because if there were, a lot more people would have
complained about it by now.  I think there's probably a bug in your
application logic, but you haven't provided enough detail to figure
out what it is.  I'd suggest examining your log files for clues, and
perhaps posting relevant sections of them here.

It's not surprising that if you're getting duplicate key errors and
you drop the index, you would then get actual duplicate keys...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"

[Dharmendra Goyal]

If you install libtermcap then it will start working good. We have
tested it at our end.

On Fri, Jan 7, 2011 at 2:24 AM, Gabe Nell  wrote:
>> There was a change in 9.0.2 to use libedit instead of readline for
>> this (readline is GPL, which is not acceptable to some people who wish
>> to use Postgres in other products). One of my colleagues has tested
>> the issue reported and confirmed that installing the OS's termcap
>> package should solve the problem.
>
> Ubuntu doesn't seem to use termcap, an apt-cache search for termcap
> turns up nothing relevant. I did some searching and the closest
> suggestion I could find was to install libncurses5-dev, but this
> didn't help. Can you suggest that the appropriate package to install
> on Ubuntu?
>
> Thanks!
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>



-- 
Dharmendra Goyal
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +91-20-30589493
Mobile: +91-9552103323

Website: http://www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"

[Gabe Nell]

> If you install libtermcap then it will start working good. We have
> tested it at our end.

Thanks Dharmendra, however in Ubuntu there is no package called
libtermcap, though it has been suggested that the libncurses5-dev
package provides this [1]. However I tried this and I still get the
same error. Do you know the exact Ubuntu package that I need to
install?

Thanks!

Gabe

[1] http://ubuntuforums.org/showthread.php?t=1329390

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs