Le 27/09/2010 02:20, Fujii Masao a écrit :
> On Mon, Sep 27, 2010 at 9:09 AM, Gurjeet Singh
> wrote:
>> See the nuggets hidden in section 25.2.5.2. "Monitoring" at
>> http://www.postgresql.org/docs/9.0/static/warm-standby.html#STREAMING-REPLICATION
>>
>> After an UPDATE, your application can cach
On Mon, Sep 27, 2010 at 9:09 AM, Gurjeet Singh wrote:
> See the nuggets hidden in section 25.2.5.2. "Monitoring" at
> http://www.postgresql.org/docs/9.0/static/warm-standby.html#STREAMING-REPLICATION
>
> After an UPDATE, your application can cache the info from
> 'pg_current_xlog_location()' resul
On Mon, Sep 27, 2010 at 1:51 AM, Yang Zhang wrote:
> Say you have an application using PG asynchronous streaming
> replication to some hot standbys, to distribute the read load. The
> application itself is a typical web application consisting of multiple
> servers, serving a number of sessions (p
Say you have an application using PG asynchronous streaming
replication to some hot standbys, to distribute the read load. The
application itself is a typical web application consisting of multiple
servers, serving a number of sessions (perhaps belonging to different
users), and the workload is OLT