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

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.

Any ideas?

Charlie Crissman

Charlie Crissman
Sr. Oracle DBA
Oracle Certified Professional DBA
No Boundaries Network, Inc.
904-245-6839
Pager 904-840-3684
mailto:CCrissman@nbibx.com <mailto:CCrissman@nbibx.com>
Before you criticize someone, you should walk a mile in their shoes.
That way, when you criticize them, you're a mile away and you have their
shoes.

Charlie Crissman <CCrissman@nbibx.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