Explore information related to postgresql error


PostgreSQL Error code 23505 - Fix it Now ?

This article covers methods to fix PostgreSQL Error code 23505 for our customers. This issue happens when you are trying to insert a value in a column that already exists there. If you have a sequencer on the field (like with a serial column type), it is likely out of sync with the table because you have done an insert and supplied a value (rather than letting the "default" mechanism handle it by getting the nextval from the sequencer). If this is the case, reset the sequencer with a setval statement to the max value of the field.


PostgreSQL Error code 42703 - Fix it Now ?

This article covers steps to resolve PostgreSQL Error code 42703 for our customers. PostgreSQL database 42703 error triggers an error message "column does not exist" which indicates either that the requested column does not it exist, or that the query is not correct.

There are many possible reasons for this issue.

To get started, check your query for any mistakes. Often, the error is caused by a lack of quotes.

If this is the case, add double quotes to the column name, then try again. 


pgAdmin "connection to the server has been lost" - Fix it Now ?

This article covers methods to resolve pgAdmin "connection to the server has been lost" error for our customers. When connecting to a PostgreSQL server, you may get this error message. From the error message you will be able to resolve the problem. 


If pgAdmin displays this message, there are two possible reasons for this:

  • the database server isn't running - simply start it.
  • the server isn't configured to accept TCP/IP requests on the address shown.


For security reasons, a PostgreSQL server "out of the box" doesn't listen on TCP/IP ports. Instead, it must be enabled to listen for TCP/IP requests. This can be done by adding listen_addresses=’*’; this will make the server accept connections on any IP interface.


"FATAL: no pg_hba.conf entry" – How to fix the PostgreSQL error ?

This article covers methods to resolve "FATAL: no pg_hba.conf entry" error. Basically, the "no pg_hba.conf entry" can happen due to missing entries in the configuration file. 


A quick way to fix this PostgreSQL server error is to do the following steps:

1. Add or edit the following line in your postgresql.conf :

listen_addresses = '*'

2. Add the following line as the first line of pg_hba.conf. It allows access to all databases for all users with an encrypted password:

# TYPE DATABASE USER CIDR-ADDRESS  METHOD
host  all  all 0.0.0.0/0 md5

3. Restart Postgresql after adding this with service postgresql restart or the equivalent command for your setup.


"psql :could not connect to server: no route to host" - Fix it Now ?

This article covers how to fix the "could not connect to server: No route to host" PostgreSQL error. Basically, the "could not connect to server: No route to host" triggers while connecting to PostgreSQL due to a number of reasons.

Make the Iptables rules different in Master and Slave.

iptables -L INPUT
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F INPUT 
iptables -F OUTPUT
iptables  -F FORWARD


"403 forbidden" error in phppgadmin - Fix it Now ?

This article covers methods to tackle "403 forbidden" error messages in phpPgAdmin. Basically, the "Forbidden" error happens while accessing phpPgAdmin when permissions in the phpPgAdmin configuration file are not intact. 


To resolve 403 forbidden error, In the Apache configuration, simply replace:

<Directory /usr/share/phppgadmin>
    DirectoryIndex index.php
    Order deny,allow
    Allow from all
</Directory>

With:

<Directory /usr/share/phppgadmin>
   Require all granted
</Directory>



For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com