Tag Info

New answers tagged

6

Just restarting postgres is not a long term solution, you will hit the limit again, unless you have physical resource constraints on the server such as memory. During the issue the number of processes opened(nproc) by postgres user was 503 and the estimated number of open files(nofile) was 35225 and yet your postgres_limits.conf shows that you have set nproc ...


2

If you don't want to restart the server and just send a signal to postgreSQL, just type command: pg_ctl reload


1

At least for version 9.4, an identical filesystem path needs to exist on the standby(s). From http://www.postgresql.org/docs/9.4/static/warm-standby.html#STANDBY-PLANNING: "In particular, the path names associated with tablespaces will be passed across unmodified, so both primary and standby servers must have the same mount paths for tablespaces if that ...


2

On systemd based systems like RHEL/CentOS 7 and Fedora the procedure for running initdb is somewhat different. This is no longer done by the init scripts (which no longer exist), and the new procedure is much closer to the upstream instructions. You must first su to the postgres user, and then run initdb or pg_ctl initdb. It's not necessary to provide a ...


0

Migration plan: 1) Upgrade your PG on production server. For fast upgrade use pg_upgrade with -k option (WARNING!!! Read manual http://www.postgresql.org/docs/9.4/static/pgupgrade.html) 2) After upgrade PG setup replication from prod to new server. 3) Promote replica as new PG. Profit.


2

The most likely explanation is that there is a service already on that port, but you don't see it in Task Manager because by default it will only show tasks owned by your user. Check the netstat command's output, when run in an Administrator command prompt. Also look in services.msc for a postgresql-9.4-x86 service that might be running. Note that in ...


2

You have understood the concept of listen addresses wrong. listen_addresses is the list of IP addresses of the interfaces on the server running PostgreSQL, which can be used to connect to the PostgreSQL service. So, for example, your PostgreSQL server has the IP address 192.168.10.1, you specify: listen_addresses 'localhost,192.168.10.1'; This means ...


0

Hi I had same issue while working on cloud linux machine with postgresql server 9.4 and I solved this by making below mentioned entry in pg_hba.conf file. host all all 0.0.0.0/0 md5


0

After some years in the trench, my answer is ZFS and SmartOS. Here's a paper on the benchmarks: https://www.joyent.com/public-cloud/benchmarks/postgresql


2

I have found the problem. I edited a setting that deals with Track Fade In. In doing so from 0.50 to 1. Leaving the . exposed at the end and bungling the database. Thank You



Top 50 recent answers are included