> With the patch applied, I let an inhouse stress test run for
> several hours and it completed without incident. I also ran
> two runs of pgbench with 50 connections x 1000 transactions
> and one run of 50 connections x 5000 transactions. All
> completed successfully. (Test server is a dual
Test server has SP1. This bug has only bit us twice (and never in a
testing environment) so it's hard to say (from our experience).
The successful pgbench runs are definitely good to see though.
Pete
>>> "Magnus Hagander" <[EMAIL PROTECTED]> 05/02/06 10:14 am >>>
Great news. One question though
The following bug has been logged online:
Bug reference: 2417
Logged by: James
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Microsoft Windows XP Professional
Description:bug for finding string in column
Details:
hi,
i've encounter bug
The following bug has been logged online:
Bug reference: 2418
Logged by: James
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Microsoft Windows XP Professional
Description:number & date & time
Details:
hi,
we would like to have convinien
On Tue, 2 May 2006, James wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2417
> Logged by: James
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Microsoft Windows XP Professional
> Description:bug for finding st
On Tue, May 02, 2006 at 10:34:12 +,
James <[EMAIL PROTECTED]> wrote:
>
> i've encounter bug where when a field is empty / null (type varchar(255) ),
> when i use the sql query <> 'myvalue', it seems to be false all the time.
Empty and NULL are not the same thing. NULL <> to any value evalua
On Tue, May 02, 2006 at 10:36:52 +,
James <[EMAIL PROTECTED]> wrote:
>
> we would like to have convinience data conversion from datatype number of
> value '' as null and datatype date / timestamp / timestampz of value '' as
> null...
>
> so far, postgresql will reject those value for number
