ersion.
Is the new 9.1.3 PostgreSQL using some of the patches recommended in that
article that would enhance multi-core scalability?
Thank you very much for your attention,
Constantin Teodorescu
Csaba Nagy wrote:
Constantin,
What binding are you using ? We here use Java+JDBC, and we were able to
get stable query plans by forcing server side prepared statements (using
PGStatement#setPrepareThreshold with 1 as the threshold), where the
query is prepared without knowing the parameter value
on the developers, it does not change anything in what have
been done since now and it allows the developers and database
administrators to dive into the query plan ocean and to get out of there
the best of the quickest of the fastest query plan. :-)
Hope that this long message hav
very workstation
database in a separate schema in the central database that mean that I will
have 3500 different schemas.
Is there any limit or any barrier that could stop this kind
of approach or make things go slower?
Constantin Teodorescu
Ancient PgAccess developer
P.S. Please Cc: m
pecified directly in pgaccess.
But libpq library need to be found automatically because it isn't in a "load"
explicit command.
Constantin Teodorescu
