Alan T DeKok writes:
> Magnus Hagander wrote:
>> If you can test the complete patch in your environment (particularly
>> if you already have a "bad packet injector" that you know creates the
>> issue on 9.0), that would be great though.
>
> If you use FreeRADIUS, use "radclient" to send the foll
Magnus Hagander wrote:
> If you can test the complete patch in your environment (particularly
> if you already have a "bad packet injector" that you know creates the
> issue on 9.0), that would be great though.
If you use FreeRADIUS, use "radclient" to send the following text:
User-Name = "bob"
On Tue, Oct 5, 2010 at 19:11, Alan T DeKok wrote:
> Magnus Hagander wrote:
>> Actually, nevermind that one. Here's a patch I worked up from your
>> description, and that turns out to be fairly similar to yours in what
>> it does I think - except I'm not rearranging the code into a separate
>> func
That was a short form i used to point out the issue, the actual code
from src/interfaces/libpq/fe-exec.c
1368 static bool
1369 PQexecStart(PGconn *conn)
1370 {
1371 PGresult *result;
1372
1373 if (!conn)
1374 return false;
1375
1376
Boris Bondarenko writes:
> That was a short form i used to point out the issue, the actual code
> from src/interfaces/libpq/fe-exec.c
Oh. Well, you didn't actually explain under what conditions you think
that fails. Since that code hasn't changed in quite a few releases,
and is extremely heav
"Boris" writes:
> while ((result = PQgetResult(conn)) != NULL){
> ExecStatusType resultStatus = result->resultStatus;
> PQclear(result); /* only need its status */
> /* check for loss of connection, too */
> if (result->resultStatus == PGRES_COPY_IN ||
> r
The following bug has been logged online:
Bug reference: 5697
Logged by: Boris
Email address: ad...@nyc.yamaha.com
PostgreSQL version: 8.3.5
Operating system: Linux RH ES5
Description:Infinite loop inside PQexecStart function
Details:
The infinite loop in this case
On Thu, Oct 7, 2010 at 3:00 PM, Tony Marston
wrote:
> My processor is 32 bit and my OS is 32 bit.
Sounds like the existing check is broken then Dharmendra. Please take
a look when you get a moment.
Thanks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http:
On Thu, Oct 7, 2010 at 2:14 PM, Dharmendra Goyal
wrote:
> Hi Dave,
> We do not allow 64 bit installer to run on 32 bit windows and this check is
> already there.
Oh, hmm. Tony, are you running the 64bit version of XP? I assumed not,
as it's pretty rare, but
--
Dave Page
Blog: http://pgsnake
Hi Dave,
We do not allow 64 bit installer to run on 32 bit windows and this check is
already there.
Regards,
Dharmendra
On Thu, Oct 7, 2010 at 5:13 PM, Dave Page wrote:
> On Thu, Oct 7, 2010 at 12:40 PM, Tony Marston
> wrote:
> > I found the log file, and when it looked at it there was a refe
On Thu, Oct 7, 2010 at 12:40 PM, Tony Marston
wrote:
> I found the log file, and when it looked at it there was a reference to the
> 64 bit version of Windows, which I don't have. I downloaded the 32 bit
> version (which I'm sure I did the first time, but I must have been wrong),
> ran it, and it
On Thu, Oct 7, 2010 at 11:10 AM, Tony Marston
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5696
> Logged by: Tony Marston
> Email address: t...@marston-home.demon.co.uk
> PostgreSQL version: 9.0
> Operating system: Widows XP
> Description: can
The following bug has been logged online:
Bug reference: 5696
Logged by: Tony Marston
Email address: t...@marston-home.demon.co.uk
PostgreSQL version: 9.0
Operating system: Widows XP
Description:cannot upgrade to 9.0.1
Details:
I have just installed version 9.0, and
13 matches
Mail list logo
