We are trying to determine the best solution for a web based
application. We have 13 databases (separate postmaster for each
database) that we need to retrieve data from in order to produce the web
page. This data is changing on a regular basis. Question is:
1. Do we:
for database in
Geoffrey wrote:
We are trying to determine the best solution for a web based
application. We have 13 databases (separate postmaster for each
database) that we need to retrieve data from in order to produce the
web page. This data is changing on a regular basis. Question is:
1. Do we:
On 18/03/2010 9:19 PM, Geoffrey wrote:
We are trying to determine the best solution for a web based
application. We have 13 databases (separate postmaster for each
database) that we need to retrieve data from in order to produce the web
page. This data is changing on a regular basis.
A quick
Craig Ringer wrote:
On 18/03/2010 9:19 PM, Geoffrey wrote:
We are trying to determine the best solution for a web based
application. We have 13 databases (separate postmaster for each
database) that we need to retrieve data from in order to produce the web
page. This data is changing on a
Yeb Havinga wrote:
3. Like 1 but with the use of a connection pooler like pgpool. Not
sure if pgpool supports asynchronous queries, but that would help as
well by pulling data from the 13 databases in parallel instead of
serial: get the queries onto the 13 servers without waiting for
results,
