Thread: 7.0 configuration
Hello, I have just updated to 7.0 and have observed the following: When the system boots, and Postgres is attempting to start, I get the following error: 564, unary operator expected. Yet after boot, I can see that postmaster is running and I can connect to it with my application. [root@Belcher jbelcher]# ps -aef | grep post postgres 559 1 0 07:33 ? 00:00:00 [pg_ctl] postgres 561 559 0 07:33 ? 00:00:00 /usr/bin/postmaster -i postgres 899 561 0 07:34 ? 00:00:00 /usr/bin/postgres localhost root root 991 985 0 07:35 ttyp0 00:00:00 grep post Previous to this reboot, I was not able to run psql, it failed with a statement that I had "Too many clients".(there were none). After the reboot, I was able to connect with psql even with the above error. Anyone have any idea what going on? Jim
"Belcher, Jim" <JBelcher@elastic.com> writes: > When the system boots, and Postgres is attempting to > start, I get the following error: 564, unary operator expected. I don't believe any part of Postgres itself issues such an error code. Perhaps the message is coming out of your shell, which would suggest some portability problem in the pg_ctl shell script. Try running pg_ctl by hand and/or inserting debugging echo commands to see if you can narrow down where the problem is. What platform are you on, anyway? regards, tom lane
On occasions I have had similar errors when starting up. I'm using Mandrake 7.0.3-2mdk RPMs on Mandrake 7.2. The server still starts and runs OK.
Have done a complete reinstall since the last time I had this error so can be of little more help.
Regards
Ben
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 03 February 2001 20:18
> To: Belcher, Jim
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] 7.0 configuration
>
>
> "Belcher, Jim" <JBelcher@elastic.com> writes:
> > When the system boots, and Postgres is attempting to
> > start, I get the following error: 564, unary operator expected.
>
> I don't believe any part of Postgres itself issues such an error code.
> Perhaps the message is coming out of your shell, which would suggest
> some portability problem in the pg_ctl shell script. Try running
> pg_ctl by hand and/or inserting debugging echo commands to see if you
> can narrow down where the problem is.
>
> What platform are you on, anyway?
>
> regards, tom lane
>