hi,
this is strange: one connection almost killed the server. So not a
combination of a lot of connections. I saw one connection grewing till over
100GB. Then I cancelled the connection before the oom killer became active
again.
These are my memory settings:
shared_buffers = 20GB
temp_buffers =
Bert bier...@gmail.com writes:
These are my memory settings:
work_mem = 4GB
How is it possible that one connection (query) uses all the ram? And how
can I avoid it?
Uh ... don't do the above. work_mem is the allowed memory consumption
per query step, ie per hash or sort operation. A
I hope this is the correct mailing list for installation issues.
We currently have postgresql84-8.4.5 installed on our server. I would like to
upgrade it to postgresql84-8.4.17. However, the rhel-x86_64-server-5 repo only
goes up to postgresql84-8.4.13.
Is there another repo I can use for the
Hi,
http://yum.postgresql.org/8.4/redhat/rhel-5Server-x86_64/
I can see 8.4.17 there. Maybe you checked somewhere else?
Regards, Devrim
John Reeve jre...@pelagodesign.com wrote:
I hope this is the correct mailing list for installation issues.
We currently have postgresql84-8.4.5 installed
Devrim,
Yes, I checked there. The problem is the package names don't match. I currently
have a package named postgresql84 installed. The postgresql.org repo has the
postgresql package. Is it possible to upgrade postgresql84 using the RPM
from postgresql ?
Regards,
John
From: Devrim Gündüz
Hi,
Ahh, you are using Red Hat's packages. Community packages support postgresql84
naming scheme for RHEL 6. You may want to pester Red Hat for updated packages
(i.e. Tom), or use ours (which is fully compatible with RH packages). Usually
community pushes updates quicker.
I am sure you can
=?ISO-8859-1?Q?Devrim_G=FCnd=FCz?= dev...@gunduz.org writes:
http://yum.postgresql.org/8.4/redhat/rhel-5Server-x86_64/
I can see 8.4.17 there. Maybe you checked somewhere else?
I suppose he's asking about the official RHEL packages, which indeed
are only at 8.4.13. The right way to make
Tom,
That is correct. I was hoping for the official RHEL packages. I think I'll
instead put our efforts towards upgrading to 9.2 and using the
yum.postgresql.org repo to do so. I was hoping for some interim patches before
we upgrade, but that is not going to happen. Time to just do the
Hi,
The server was running correctly.
I didn't changed the configuration.
I did an apt-get upgrade and it didn't restarted.
The problem is maybe not related to the upgrade but appeared during the
restart.
I did the same upgrade on another (very similar) server and didn't have
any problem.
PostgreSQL 9.2.4
I just upgraded Postgresql from source from 9.2.3 to 9.2.4. I did the gmake
world and gmake install-world. I did exactly the same thing I did with 9.2.3.
For some reason when I try to access my database on the local machine with the
below command I get the following error:
Campbell, Lance la...@illinois.edu writes:
Error:
psql: symbol lookup error: psql: undefined symbol: PQconnectdbParams
This looks like psql is picking up a rather ancient version of libpq.so.
Applying ldd or local equivalent to the psql executable would help you
figure out where it's getting
I just found an old posting from 2010-08-15. I added the below. If fixed the
issue. But I have never had to add this before. I don't manage the server I
run the database on. It might be the case that there was an upgrade of Red Hat
since the last time I installed that is causing this to be
I managed to solve the problem.
For the record, I did the following:
mkdir -p ~/postgresql/{etc,lib,log}
cp -a /etc/postgresql/9.1/main ~/postgresql/etc/old-install
cp -a /var/lib/postgresql/9.1/main ~/postgresql/lib/old-install
cp -a /var/log/postgresql ~/postgresql/log/old-install
apt-get
I figured it all out. When I ran the configuration script I told it to put the
code in pgsql-9.2.4. Then after the code installed I moved it to pgsql-9.2.
Then the install could not find the proper libraries. So it used the system
one. I reinstalled but this time with the target directory
Campbell, Lance la...@illinois.edu writes:
I figured it all out. When I ran the configuration script I told it to put
the code in pgsql-9.2.4. Then after the code installed I moved it to
pgsql-9.2. Then the install could not find the proper libraries. So it used
the system one. I
15 matches
Mail list logo
