Fernezelyi Marton wrote:
>
> We would like to reach at least 15-20 query per second, 95 percent
> SELECT id FROM mail WHERE name='name' queries. The rest is SELECT pers or
> UPDATE in one of the two tables.
>
> When the number of concurrent queries is 30 or higher, the postgres
> answers very slowly, and it writes
>
> NOTICE: SIAssignBackendId: discarding tag 2147339305
> FATAL 1: Backend cache invalidation initialization failed
>
> messages to the log.
>
> If the number of concurrencies are 10, then everything goes fine, but the
> number of queries/sec are 8. Is this the maximum loadability of postgres?
I hope that both issues will be addressed in 6.4 by removing
invalidation code and skipping fsync() after each SELECT...
Vadim
