Hi All,
We are planning to create a 2nd instance of postgres db in the same server.
The reason is simple. After we added another application, the number of
WAL(s) created is too much. So we want to separate the db by moving it out
to another instance of postgres in the same machine. We want to stu
Hi,
thats possible. Dont forget so set another port in your postgresql.conf
Thomas
Am 13.12.2011 09:23, schrieb Selva manickaraja:
Hi All,
We are planning to create a 2nd instance of postgres db in the same
server. The reason is simple. After we added another application, the
number of WAL(
Thomas Markus writes:
> thats possible. Dont forget so set another port in your postgresql.conf
I think actually the reason pg_ctl is complaining is that it doesn't
know how to read postgresql.conf, so it's unaware that the second server
is supposed to be on 5433. (IIRC, this is fixed in 9.1, bu
On Tue, Dec 13, 2011 at 1:23 AM, Selva manickaraja wrote:
> Hi All,
>
> We are planning to create a 2nd instance of postgres db in the same server.
> The reason is simple. After we added another application, the number of
You don't mention which OS you're running, but any debian based Linux
distr
Hello Andreas,
thank you very much for the link.
Original-Nachricht
> Datum: Thu, 08 Dec 2011 13:04:30 +0100
> Von: lst_ho...@kwsoft.de
> Zitat von Jan-Peter Seifert :
> > I wonder whether the number of connections is still limited on
> > Windows 64-bit if you also use a 64-b
Hi All;
I just installed Fedora 16, I was running fedora 14.
I installed Postgresql from source and set SHMMAX to 2198066816
I set postgres to use 2GB for shared_buffers and I get this when I try
to start:
FATAL: shmat(id=4096103) failed: Cannot allocate memory
The only real difference fro
CS DBA writes:
> I set postgres to use 2GB for shared_buffers and I get this when I try
> to start:
> FATAL: shmat(id=4096103) failed: Cannot allocate memory
> The only real difference from Fedora 14 is that on Fedora 16 I'm using
> the PAE kernel
That's not really surprising in a 32-bit envir