[BUGS] BUG #5465: dblink TCP connection hangs blocking translation from being terminated

2010-05-19 Thread Valentine Gogichashvili
The following bug has been logged online: Bug reference: 5465 Logged by: Valentine Gogichashvili Email address: val...@gmail.com PostgreSQL version: 8.2.1 Operating system: Red Hat 3.4.6-3 (kernel 2.6.9-42.0.3.ELsmp) Description:dblink TCP connection hangs blocking tr

[BUGS] BUG #5464: ecpg on 64bit system converts "long long" to "long"

2010-05-19 Thread Michael Enke
The following bug has been logged online: Bug reference: 5464 Logged by: Michael Enke Email address: michael.e...@wincor-nixdorf.com PostgreSQL version: 8.4.4 Operating system: Linux Description:ecpg on 64bit system converts "long long" to "long" Details: This appli

Re: [BUGS] BUG #5465: dblink TCP connection hangs blocking translation from being terminated

2010-05-19 Thread Magnus Hagander
On Wed, May 19, 2010 at 5:10 AM, Valentine Gogichashvili wrote: > > The following bug has been logged online: > > Bug reference:      5465 > Logged by:          Valentine Gogichashvili > Email address:      val...@gmail.com > PostgreSQL version: 8.2.1 > Operating system:   Red Hat 3.4.6-3 (kernel

Re: [BUGS] BUG #5464: ecpg on 64bit system converts "long long" to "long"

2010-05-19 Thread Michael Meskes
On Wed, May 19, 2010 at 08:53:12AM +, Michael Enke wrote: > If you run it through ecpg, in the resulting c file > the variable test has type long on 64 bit system. > On 32 bit system it is long long. Apparently when this code was written "long long" was 64bit, but it doesn't seem to be that wa

Re: [BUGS] BUG #5464: ecpg on 64bit system converts "long long" to "long"

2010-05-19 Thread John R Pierce
Michael Meskes wrote: On Wed, May 19, 2010 at 08:53:12AM +, Michael Enke wrote: If you run it through ecpg, in the resulting c file the variable test has type long on 64 bit system. On 32 bit system it is long long. Apparently when this code was written "long long" was 64bit, but i

[BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Dmitry Funk
The following bug has been logged online: Bug reference: 5466 Logged by: Dmitry Funk Email address: dif...@gmail.com PostgreSQL version: 8.4.4 Operating system: Windows 2003 R2 Description:Asia/Novosibirsk timezone problem Details: Current system timezone: Asia/Novo

Re: [BUGS] BUG #5464: ecpg on 64bit system converts "long long" to "long"

2010-05-19 Thread Michael Meskes
On Wed, May 19, 2010 at 10:34:42AM -0700, John R Pierce wrote: > I'm pretty sure it varies with the 64 bit system. I believe on IBM > Power, LONG LONG *is* 64 bit. I'm currently without real access to a 64bit system until I come back home. If it is 64bit on *all* 64bit systems the problem is slig

Re: [BUGS] BUG #5465: dblink TCP connection hangs blocking translation from being terminated

2010-05-19 Thread Joseph Conway
Magnus Hagander wrote: > On Wed, May 19, 2010 at 5:10 AM, Valentine Gogichashvili > wrote: >> The following bug has been logged online: >> >> Bug reference: 5465 >> Logged by: Valentine Gogichashvili >> Email address: val...@gmail.com >> PostgreSQL version: 8.2.1 >> Operating sy

Re: [BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Alvaro Herrera
Excerpts from Dmitry Funk's message of mié may 19 13:44:35 -0400 2010: > Description:Asia/Novosibirsk timezone problem > Details: > > Current system timezone: Asia/Novosibisk > > PostgreSQL on query "show timezone" show answer "Asia/Almaty" > > Asia/Novosibisk has daylight saving time

Re: [BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Magnus Hagander
On Wed, May 19, 2010 at 3:00 PM, Alvaro Herrera wrote: > Excerpts from Dmitry Funk's message of mié may 19 13:44:35 -0400 2010: > >> Description:        Asia/Novosibirsk timezone problem >> Details: >> >> Current system timezone: Asia/Novosibisk >> >> PostgreSQL on query "show timezone" show answe

Re: [BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Alvaro Herrera
Excerpts from Magnus Hagander's message of mié may 19 15:03:25 -0400 2010: > On Wed, May 19, 2010 at 3:00 PM, Alvaro Herrera > wrote: > > Excerpts from Dmitry Funk's message of mié may 19 13:44:35 -0400 2010: > >> Current system timezone: Asia/Novosibisk > >> > >> PostgreSQL on query "show timez

Re: [BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Magnus Hagander
On Wed, May 19, 2010 at 3:12 PM, Alvaro Herrera wrote: > Excerpts from Magnus Hagander's message of mié may 19 15:03:25 -0400 2010: >> On Wed, May 19, 2010 at 3:00 PM, Alvaro Herrera >> wrote: >> > Excerpts from Dmitry Funk's message of mié may 19 13:44:35 -0400 2010: > >> >> Current system time

Re: [BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Alvaro Herrera
Excerpts from Magnus Hagander's message of mié may 19 15:17:50 -0400 2010: > > > Well, ISTM it does make a difference, which is that there *is* DST info > > in the N. Central Asia Standard Time zone, no?  According the Dmitry, > > Almaty doesn't have DST, so it's wrong to report that zone. > > Wel

Re: [BUGS] BUG #5466: Asia/Novosibirsk timezone problem

2010-05-19 Thread Tom Lane
Alvaro Herrera writes: > Excerpts from Magnus Hagander's message of mié may 19 15:17:50 -0400 2010: >> Well, if we report it as Novosibirsk, it will have DST. Which users in >> Almaty aren't supposed to have, so it'll be wrong for them. So it's >> going to be wrong for one of them whichever way w

Re: [BUGS] BUG #5464: ecpg on 64bit system converts "long long" to "long"

2010-05-19 Thread Michael Enke
Michael Meskes schrieb: > On Wed, May 19, 2010 at 10:34:42AM -0700, John R Pierce wrote: >> I'm pretty sure it varies with the 64 bit system. I believe on IBM >> Power, LONG LONG *is* 64 bit. > > I'm currently without real access to a 64bit system until I come back home. If > it is 64bit on *all*