Re: psql dies if I use non-default MaxBackends & NBuffers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Charlie Crissman <CCrissman(at)nbibx(dot)com>
Cc: "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: psql dies if I use non-default MaxBackends & NBuffers
Date: 2000-12-29 21:03:13
Message-ID: 24122.978123793@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Charlie Crissman <CCrissman(at)nbibx(dot)com> writes:
> I have a weird one... when I start my postmaster with non-default
> MaxBackends & NBuffers (I am using 64 & 128 respectively, in this example),
> I try to connect via psql and psql quits after I enter my password. Even if
> I set them to the default (using -o "-N 32 -B 64"), the same thing happens.
> If I leave that off of my startup command, psql connects ok.

Try looking in the postmaster log. I suspect you will find a complaint
about bad command line parameters there...

If you are actually doing it just as you show above, the problem is that
-N and -B are postmaster switches not backend switches. They don't go
into the argument of -o.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Stephan Szabo 2000-12-29 23:15:08 Re: pg_dumap not include foreign key...
Previous Message Charlie Crissman 2000-12-29 18:55:05 psql dies if I use non-default MaxBackends & NBuffers