On 21.09.2012 14:18, Amit kapila wrote:
On Tuesday, September 18, 2012 6:02 PM Fujii Masao wrote:
On Mon, Sep 17, 2012 at 4:03 PM, Amit Kapilaamit.kap...@huawei.com wrote:
Approach-2 :
Provide a variable wal_send_status_interval, such that if this is 0, then
the current behavior would prevail
Apologies for delay in progressing this, but I only have access to an
AIX7.1 system periodically.
Just to confirm that source build of 9.2.1 release now builds clean
against AIXv7.1 with xlc v12.1 compiler.
Thanks,
Andrew
On 31/08/12 20:20, Tom Lane wrote:
Andrew Hastieand...@ahastie.net
On Mon, Oct 1, 2012 at 6:38 AM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
Hmm, I think we need to step back a bit. I've never liked the way
replication_timeout works, where it's the user's responsibility to set
wal_receiver_status_interval replication_timeout. It's not very
Does anyone know of any known issues (show-stoppers) with upgrading to
Postgresql 9.2 but retaining Postgis 1.5.3 or Postgis 1.5.5?
Thanks
Excerpts from Robert Haas's message of lun oct 01 21:02:54 -0300 2012:
On Mon, Oct 1, 2012 at 12:57 PM, Fujii Masao masao.fu...@gmail.com wrote:
I believe many users are basically familiar with TCP keepalives and how to
specify it. So I think that this approach would be intuitive to users.
