"Pavel Golub" <[EMAIL PROTECTED]> writes:
> 1. Connect to server.
> 2. Execute some queries, e.g. SELECT 2;
> 3. Wait for a while (to be sure I suggest 20 minutes)
> 4. Try to execute query, e.g. SELECT version()
> We got an error: "server closed the connection unexpectedly. This probably
> means
The following bug has been logged online:
Bug reference: 2570
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.x
Operating system: Windows XP
Description:Connection closed unexpectedly
Details:
Bug may be reproduced by any tool using l
On Wed, 2006-08-09 at 05:31 +, [EMAIL PROTECTED] wrote:
> On Mon, Aug 07, 2006 at 09:40:59PM +, PFudd wrote:
> >
> > The following bug has been logged online:
> >
> > Bug reference: 2565
> > Logged by: PFudd
> > Email address: [EMAIL PROTECTED]
> > PostgreSQL version: 8
This isn't a bug; moving to pgsql-performance.
On Tue, Aug 08, 2006 at 08:42:02AM +, kumarselvan wrote:
> i have installed the postgres as mentioned in the Install file. it is a 4
> cpu 8 GB Ram Machine installed with Linux Enterprise version 3. when i am
> running a load which will perfrom 40
"Brian C. DeRocher" <[EMAIL PROTECTED]> writes:
> It appears that when you create a view of a union, numeric data types
> loose their scale and precision.
I think this is the same issue discussed here:
http://archives.postgresql.org/pgsql-hackers/2004-12/msg00408.php
That was just before 8.0 rele
It appears that when you create a view of a union, numeric data types
loose their scale and precision.
db=> create table t1 (c1 numeric(4,2));
CREATE TABLE
db=> create view v1 as select c1 from t1;
CREATE VIEW
db=> \d v1
View "brian.v1"
Column | Type | Modifiers
+-
OK, done.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Seems like this probably ought to round up not down:
>
> > I thought about that, but because statement_timeout is in millis,
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Seems like this probably ought to round up not down:
> I thought about that, but because statement_timeout is in millis, and
> not micros, we can't have a value that gets rounded down. I am
> thinking a cleaner solution is to check f
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> ! /* WaitForSingleObjectEx() uses milliseconds */
> > ! waittime = timerCommArea.value.it_value.tv_usec
> > / 1000 + timerCommArea.value.it_value.tv_sec * 1000;
>
> Seems like this
Bruce Momjian <[EMAIL PROTECTED]> writes:
! /* WaitForSingleObjectEx() uses milliseconds */
> ! waittime = timerCommArea.value.it_value.tv_usec
> / 1000 + timerCommArea.value.it_value.tv_sec * 1000;
Seems like this probably ought to round
Please cc the list
so others can learn.
Yes, I think a
patch for this was recently committed. I know it was at least discussed
somewhere...
-Original Message-From: dror
[mailto:[EMAIL PROTECTED]Sent: Wednesday, August 09, 2006 2:17
AMTo: Jim NasbySubject: RE: [BUGS] BUG #25
I have a big "Oops" for this item. Seems in 8.0, we used the Win32 call
SetWaitableTimer(), which takes its timeout in 100 nanosecond intervals.
This was changed to use WaitForSingleObjectEx() in 8.1, but not
properly. The 8.0 code works fine.
The attached patch will fix the problem, and will b
Jim Nasby <[EMAIL PROTECTED]> writes:
>> I'm using VB6, and trying to update a table. It is all happening on
>> my home pc with IIS running too. I can download the table to a
>> datagrid, bit I can't type any text i a textbox and update it whith
>> out the error occuring. Here [skip]
> I don't kno
Hello,
i have a "new" machine with following problem:
postgres-7.4.13[7874]: [457-1] ERROR: could not open segment 1 of relation
"data_server_id_idx" (target block 791807): No such file or directory
I my point of view it seems the same error as:
http://archives.postgresql.org/pgsql-admin/2006-07
14 matches
Mail list logo
