Hot answers tagged postgresql-8.4
You need to increase the maximum size of a chunk of shared memory Linux kernel allows to allocate at once (known as SHMMAX parameter) You need to edit /etc/sysctl.conf and add the following line: kernel.shmmax = 41943040 (where 41943040 is the size of memory in bytes, i.e. 40 megabytes. On production system you probably want to set this value way higher ...
Using update-rc.d (Debian/Ubuntu): janus@Zeus:~$ sudo update-rc.d -f postgresql remove Removing any system startup links for /etc/init.d/postgresql ... /etc/rc0.d/K21postgresql /etc/rc1.d/K21postgresql /etc/rc2.d/S19postgresql /etc/rc3.d/S19postgresql /etc/rc4.d/S19postgresql /etc/rc5.d/S19postgresql /etc/rc6.d/K21postgresql ...
The simplest way to do this is open a terminal and type: sudo apt-get --purge remove postgresql This will also prompt you to remove that software that depends on Postgres, which in this case it appears you would like to do. I do not personally run 9.10 or Postgres, so it is possible that Postgres installs itself in several parts. In that case, a simple: ...
The error message refers to a Unix-domain socket, so you need to tweak your netstat invocation to not exclude them. So try it without the option -t: netstat -nlp | grep 5432 I would guess that the server is actually listening on the socket /tmp/.s.PGSQL.5432 rather than the /var/run/postgresql/.s.PGSQL.5432 that your client is attempting to connect to. ...
This issue comes form installing the postgres package with out a version number. Although postgres will be installed and it will be the correct version the script to setup the cluster will not be run correctly. It's a packaging issue. If your comfortable with Postgres there is a script you can run to crete this cluster and get postgres running however if ...
The template it is referring to is template1, which is implicitly used if you don't specify another template. The quickest workaround is that you create your database from template0 instead, using the createdb --template=template0. You may wish to drop and reinitialize your entire cluster with a more sensible locale. You have probably had your operating ...
You should choose Ubuntu 10.04 since it's a LTS (Long Time Support) release, which means it a really stable distro shipped with only stable software. Adding that you have support until 2015-04 for the server (that include security patches, and so on). It comes with postgresql 8.4.6. However if you need the new release postgresql 9.0 you can install on ...
Steps that worked for me on Ubuntu 8.04.2 to remove postgres 8.3 List All Postgres related packages dpkg -l | grep postgres ii postgresql 8.3.17-0ubuntu0.8.04.1 object-relational SQL database (latest versi ii postgresql-8.3 8.3.9-0ubuntu8.04 object-relational SQL database, ...
Using update-rc.d is better but you can do it with chkconfig: sudo apt-get install chkconfig sudo chkconfig -s postgresql off In Ubuntu 12.04, you also need to create a symlink to insserv's location: sudo ln -s /usr/lib/insserv/insserv /sbin/insserv
The various PostgreSQL command line tools will talk to the server listening on the default port (5432) by default. You can determine which port each server is listening on by looking for the port variable in the /etc/postgresql/$VERSION/main/postgresql.conf file for the relevant server. To get the command line tools to talk to the other server by default, ...
Just create a softlink like this : ln -s /tmp/.s.PGSQL.5432 /var/run/postgresql/.s.PGSQL.5432
This can help you: http://www.linuxquestions.org/questions/linux-general-1/how-to-remove-postgresql-from-startup-481963/#post2417585 But install chkconfig first: sudo apt-get install chkconfig and then use it chkconfig
You can use psql -U postgres -h localhost to force the connection to happen over TCP instead of UNIX domain sockets; your netstat output shows that the PostgreSQL server is listening on localhost's port 5432. You can find out which local UNIX socket is used by the PostgrSQL server by using a different invocavtion of netstat: netstat -lp --protocol=unix | ...
If you are referring to 9.10 and 10.04 releases, choose the 10.04 as it is LTS, the LTS release is recommended for production systems. Watch out for the file system used with PostgreSQL, there has been some regression in the performance of PostgreSQL using the ext4 file system in the past, so check if this is still the case.
There is an repo. To add it, open a terminal and entersudo touch /etc/apt/sources.list.d/pgdg.list sudo echo "deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main" | sudo tee /etc/apt/sources.list.d/pgdg.list Then import the repository signing key: wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add - sudo ...
Assuming it's installed from packages, sudo apt-get remove postgresql-8.4 Or does that not work and you need something more involved? Please post more details if so. You can get a list of relevant packages to look at removing with: dpkg -l | grep postgresql
I had to compile PostgreSQL 8.1 on Debian Squeeze because I am using Project Open, which is based on OpenACS and will not run on more recent versions of PostgreSQL. The default compile configuration puts the unix_socket in /tmp, but Project Open, which relies on PostgreSQL, would not work because it looks for the unix_socket at /var/run/postgresql. There ...
Better to go with 10 as it will have updated packages and support life span will be higher than 9.
In postgresql-8.4.postinst, the line immediately above the call to configure_version is: . /usr/share/postgresql-common/maintscripts-functions That will load all the functions from that file, which includes configure_version. That file is found in the postgresql-common package.
One command to completely remove postgresql in terminal is sudo apt-get --purge remove postgresql\*. Please note that this command will remove postgresql and all it's compenents.
I was in your position too, and I agree, it's hard to find anything at a basic enough level. Postgresql is a bit more complicated than MySQL, but it's not impossible to figure out. The greatest help I've found was this article on Linode Library: http://library.linode.com/search?query=postgresql (choose your relevant OS/version)
You can use pgadmin, a gui client for PostgreSQL for all these purpose. It is in the software center. Hope this will help you: http://www.postgresql.org/docs/8.4/interactive/index.html
maybe you need configure the locale before to create the cluster export LANGUAGE=en_US.UTF-8 export LANG=en_US.UTF-8 export LC_ALL=en_US.UTF-8 locale-gen en_US.UTF-8 dpkg-reconfigure locales
My suggestion would be to not use that all-in-one installer in the first place. Ubuntu already includes all the tools you need to make use of PostgreSQL in its software archive, including the graphical administration utility pgAdmin III. And since these programs are part of the software archive, you get the benefit of Ubuntu security updates (which you ...
This is caused due to installation of Postgre SQL was stopped in between. Purge the postgre sql installation and you will be fine. To purge postgre sql installation, in console type sudo apt-get remove --purge postgresql Trying running these commands, it should resolve it. sudo dpkg --configure -a sudo apt-get -f install sudo apt-get update && ...
Try: apt-get --purge remove postgresql\* It helped me. I had same problem. Command differs with suggestion at the end '\*'.
sudo apt-get install postgresql-8.4 Seems to do the trick (well, not really a trick).
If the old version of PostgreSQL is not available in Ubuntu repositories see PostgreSQL Apt Repository: This repository will integrate with your normal systems and patch management, and provide automatic updates for all supported versions of PostgreSQL throughout the support lifetime of PostgreSQL.
I believe you're interested in sudo apt-get build-dep postgresql-8.4.
OK, this was really, REALLY nasty because there's a dependency nest in there that just won't go away with the usual round of apt-get purge, apt-get -f install, etc. The only way around this one (I recreated your problem in a VM and tested) is just to put a directory there for apt to get rid of in the first place. root@yourbox:/# mkdir -p ...
Only top voted, non community-wiki answers of a minimum length are eligible