Can't connect to PGSQL

Started by ferdinan firmansyahover 23 years ago12 messagesgeneral
Jump to latest
#1ferdinan firmansyah
mymand@yahoo.com

We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.

1. What seems to be the problem?
2. How can I read the server's activities?(reading the
log)

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/

#2Stephan Szabo
sszabo@megazone23.bigpanda.com
In reply to: ferdinan firmansyah (#1)
Re: Can't connect to PGSQL

On Mon, 4 Nov 2002, ferdinan firmansyah wrote:

We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.

1. What seems to be the problem?
2. How can I read the server's activities?(reading the
log)

Are you allowing http connections to the server (tcpip_socket=true
in postgresql.conf) and are you allowing connections from the
machine in question (see pg_hba.conf)

#3geek24@avantel.net
geek24@avantel.net
In reply to: Stephan Szabo (#2)
About lower and uppercase

Hi!

I don't know if this is possible from postgresql configuration...

I want to ignore the use of uppercase and lowercase from the data restored
into the DB...

I mean, if I write a query like this:

select * from fruits where fruit_name like 'orange';

I could get any result where the string looks like:

orange
Orange
ORANGE

Is it possible???

Regards.

#4Stephan Szabo
sszabo@megazone23.bigpanda.com
In reply to: geek24@avantel.net (#3)
Re: About lower and uppercase

On Mon, 4 Nov 2002, [iso-8859-1] Sonia S�nchez D�az wrote:

Hi!

I don't know if this is possible from postgresql configuration...

I want to ignore the use of uppercase and lowercase from the data restored
into the DB...

I mean, if I write a query like this:

select * from fruits where fruit_name like 'orange';

I could get any result where the string looks like:

orange
Orange
ORANGE

Is it possible???

Not really without doing a little bit of changing
to the query (for example using ILIKE rather than LIKE
or lower(fruit_name) like 'orange' with an appropriate
index on lower(fruit_name).

Theoretically, it could perhaps be possible to create a locale
which compare 'orange' and 'OraNgE' equally and then
initdb in that locale, but I've never tried it so I don't
know if it'd work.

#5frbn
frbn@efbs-seafrigo.fr
In reply to: Stephan Szabo (#4)
Re: [ADMIN] About lower and uppercase

select * from fruits where fruit_name ~* 'orange';

Stephan Szabo wrote:
On Mon, 4 Nov 2002, [iso-8859-1] Sonia S?nchez D?az wrote:

Hi!

I don't know if this is possible from postgresql configuration...

I want to ignore the use of uppercase and lowercase from the data restored
into the DB...

I mean, if I write a query like this:

select * from fruits where fruit_name like 'orange';

I could get any result where the string looks like:

orange
Orange
ORANGE

Is it possible???

Not really without doing a little bit of changing
to the query (for example using ILIKE rather than LIKE
or lower(fruit_name) like 'orange' with an appropriate
index on lower(fruit_name).

Theoretically, it could perhaps be possible to create a locale
which compare 'orange' and 'OraNgE' equally and then
initdb in that locale, but I've never tried it so I don't
know if it'd work.

#6Christoph Dalitz
christoph.dalitz@hs-niederrhein.de
In reply to: frbn (#5)
Re: [ADMIN] About lower and uppercase

Date: Tue, 05 Nov 2002 09:22:37 +0100
From: frbn <frbn@efbs-seafrigo.fr>

select * from fruits where fruit_name ~* 'orange';

Does this query ever use an index on fruit_name?

AFAIK the most reliant solution is the previously suggested
"where lower(fruit_name) = 'orange'"
AND creating indices only on lower(attributename).

Beware however that there are some letters that have no
uppercase/lowercase equivalent (the letter "Eszet" (�) in German
is an example for a letter that has no uppercase equivalent).
That should not be such an issue as a proper implementation of
upper()/lower() would leave these letters alone.

Christoph Dalitz

#7geek24@avantel.net
geek24@avantel.net
In reply to: Christoph Dalitz (#6)
Re: About lower and uppercase

Thanks!!!

I use ilike and I get the result that I want...

Thanks!!!!!

Regards!

Original Message:
-----------------
From: Stephan Szabo sszabo@megazone23.bigpanda.com
Date: Mon, 04 Nov 2002 21:50:06 -0800 (PST)
To: geek24@avantel.net, pgsql-general@postgresql.org,
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] About lower and uppercase

On Mon, 4 Nov 2002, [iso-8859-1] Sonia Sánchez Díaz wrote:

Hi!

I don't know if this is possible from postgresql configuration...

I want to ignore the use of uppercase and lowercase from the data restored
into the DB...

I mean, if I write a query like this:

select * from fruits where fruit_name like 'orange';

I could get any result where the string looks like:

orange
Orange
ORANGE

Is it possible???

Not really without doing a little bit of changing
to the query (for example using ILIKE rather than LIKE
or lower(fruit_name) like 'orange' with an appropriate
index on lower(fruit_name).

Theoretically, it could perhaps be possible to create a locale
which compare 'orange' and 'OraNgE' equally and then
initdb in that locale, but I've never tried it so I don't
know if it'd work.

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

#8geek24@avantel.net
geek24@avantel.net
In reply to: geek24@avantel.net (#7)
Re: About lower and uppercase

Thanks!!!

I use ilike and I get the result that I want...

Thanks!!!!!

Regards!

Original Message:
-----------------
From: Stephan Szabo sszabo@megazone23.bigpanda.com
Date: Mon, 04 Nov 2002 21:50:06 -0800 (PST)
To: geek24@avantel.net, pgsql-general@postgresql.org,
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] About lower and uppercase

On Mon, 4 Nov 2002, [iso-8859-1] Sonia Sánchez Díaz wrote:

Hi!

I don't know if this is possible from postgresql configuration...

I want to ignore the use of uppercase and lowercase from the data restored
into the DB...

I mean, if I write a query like this:

select * from fruits where fruit_name like 'orange';

I could get any result where the string looks like:

orange
Orange
ORANGE

Is it possible???

Not really without doing a little bit of changing
to the query (for example using ILIKE rather than LIKE
or lower(fruit_name) like 'orange' with an appropriate
index on lower(fruit_name).

Theoretically, it could perhaps be possible to create a locale
which compare 'orange' and 'OraNgE' equally and then
initdb in that locale, but I've never tried it so I don't
know if it'd work.

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

#9Michiel Lange
michiel@minas.demon.nl
In reply to: ferdinan firmansyah (#1)
Re: Can't connect to PGSQL

did you start your databases with the -i option (enable TCP/IP connections)
if so, you may have a firewall or something disable port 5432
When you start your databases, how do you do so?
like: /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data -i

/log/logfile-`date +"%d-%m-%y"` 2>&1

for postmaster sends it's output to stdout, so you have to redirect it...
you can just tail the logfile, open it with vi, vim or any other texteditor,
altough I suggest you use more or tail...

"ferdinan firmansyah" <mymand@yahoo.com> schreef in bericht
news:20021105012651.62134.qmail@web14006.mail.yahoo.com...

Show quoted text

We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.

1. What seems to be the problem?
2. How can I read the server's activities?(reading the
log)

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

#10Shridhar Daithankar
shridhar_daithankar@persistent.co.in
In reply to: ferdinan firmansyah (#1)
Re: [GENERAL] Can't connect to PGSQL

On 4 Nov 2002 at 17:26, ferdinan firmansyah wrote:

We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.

1. What seems to be the problem?
2. How can I read the server's activities?(reading the
log)

See if this helps you

http://wiki.ael.be/index.php/PostgresQL101

Bye
Shridhar

--
It [being a Vulcan] means to adopt a philosophy, a way of life which islogical
and beneficial. We cannot disregard that philosophy merely forpersonal gain,
no matter how important that gain might be. -- Spock, "Journey to Babel",
stardate 3842.4

#11scott.marlowe
scott.marlowe@ihs.com
In reply to: ferdinan firmansyah (#1)
Re: [GENERAL] Can't connect to PGSQL

On Mon, 4 Nov 2002, ferdinan firmansyah wrote:

We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.

1. What seems to be the problem?

Find your postgresql.conf file i.e. 'locate postgresql.conf'.
Edit it and change this line:

tcpip_socket = false

to look like this:

tcpip_socket = true

2. How can I read the server's activities?(reading the
log)

Not sure. Look in the /var/log directory to see if RedHat sets up
postgresql to log there.

#12Thomas Swan
tswan@idigx.com
In reply to: ferdinan firmansyah (#1)
Re: Can't connect to PGSQL

ferdinan firmansyah wrote:

We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.

1. What seems to be the problem?

Check to see if you installed RedHat with firewall rules. This might
also prevent connections.