Hi ,
I guess this is not Postgres.Is it Greenplum ?
Check for max connections on master and corresponding all nodes.
Max connections at nodes has to 4-5 times the max on master.
BTW are you using simple "create as select * from table " or anything else
Abhi
Hi ,
I guess this is not Postgres.Is it Greenplum ?
Check for max connections on master and corresponding all nodes.
Max connections at nodes has to 4-5 times the max on master.
BTW are you using simple "create as select * from table " or anything else
Abhi
John P Weatherman writes:
> I am intermittently seeing a job fail with:
> ERROR: Too many updates/deletes within transaction. Reader gang not able
> to provide correct visibility (combocid.c:270) (seg1 slice1 sdw1:50002
> pid=15588)
> SQL state: XX000
A bit of searching of the archives would've
All,
I am intermittently seeing a job fail with:
ERROR: Too many updates/deletes within transaction. Reader gang not able
to provide correct visibility (combocid.c:270) (seg1 slice1 sdw1:50002
pid=15588)
SQL state: XX000
Does anyone have any ideas what this really means? So far, waiting
until
"JOE" <[EMAIL PROTECTED]> writes:
> During our load testing we saw the errors below. I believe that the "Sorry=
> , too many clients already" is because we exceeding the max connections to =
> the database.
Check.
> The "Socket command type ' unknown" error I do not understand.
The most likely
During our load testing we saw the errors
below. I believe that the "Sorry, too many clients already" is because we
exceeding the max connections to the database. The "Socket command type
'unknown" error I do not understand.
Our installation is postgres 7.2.1 on Solaris 8 sun
server. T
