Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown

2012-10-01 Thread Heikki Linnakangas
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 Kapila wrote: Approach-2 : Provide a variable wal_send_status_interval, such that if this is 0, then the current behavior would prevail and if its non-zero th

Re: [BUGS] BUG #6758: ./configure script sets HAVE_WCSTOMBS_L 1

2012-10-01 Thread Andrew Hastie
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 Hastie writes: On 31/08

Re: [BUGS] BUG #6758: ./configure script sets HAVE_WCSTOMBS_L 1

2012-10-01 Thread Andrew Hastie
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 Hastie writes: On 31/08

Re: [BUGS] BUG #7573: data loss in corner case using delete_old_cluster.sh (pg_upgrade)

2012-10-01 Thread Bruce Momjian
On Fri, Sep 28, 2012 at 01:18:26AM +, maxim.bo...@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 7573 > Logged by: Maxim Boguk > Email address: maxim.bo...@gmail.com > PostgreSQL version: 9.2.0 > Operating system: Linux > Descriptio

Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown

2012-10-01 Thread Robert Haas
On Mon, Oct 1, 2012 at 6:38 AM, Heikki Linnakangas 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 > user-friendly. I'd rather not

Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown

2012-10-01 Thread Fujii Masao
On Mon, Oct 1, 2012 at 7:38 PM, Heikki Linnakangas 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 > user-friendly. I'd rather not

[BUGS] Postgres 9.2 with Postgis 1.5.3 Upgrade

2012-10-01 Thread Freddie Burgess
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

Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown

2012-10-01 Thread Robert Haas
On Mon, Oct 1, 2012 at 12:57 PM, Fujii Masao 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. My experience is that many users are unfamiliar with TCP keepalives and that when given the opt

Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown

2012-10-01 Thread Alvaro Herrera
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 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. > > My experience

Re: [BUGS] BUG #7574: CASE in WHERE condition change result set

2012-10-01 Thread Alvaro Herrera
Excerpts from urvancevav's message of vie sep 28 05:58:42 -0300 2012: > The following bug has been logged on the website: > > Bug reference: 7574 > Logged by: Andrei > Email address: urvance...@gmail.com > PostgreSQL version: 9.2.1 > Operating system: 3.2.0-31-generic #50-Ubun