I've compiled 8.3 devel from
the latest nightly snapshot tarball, did an initdb
and when run, it crash by logging the same messages.
Jean-Pierre Pelletier
From: Alvaro Herrera <[EMAIL PROTECTED]>
To: JEAN-PIERRE PELLETIER <[EMAIL PROTECTED]>
CC: pgsql-bugs@postgresql.org
S
I've compiled the 8.2.0 sources from
http://www.postgresql.org/ftp/source/v8.2/
and when run, it crash by logging the same messages.
I'll compile from the nightly snapshot tarball (which is probably 8.3 ?) and
will post
the result.
Jean-Pierre Pelletier
From: Alvaro Herre
within
another plpgsql function but then it got back to crashing.
Thanks,
Jean-Pierre Pelletier
e-djuster
To Reproduce:
CREATE TABLE Claim (
ClaimIdINTEGER NOT NULL,
AssociatePersonId INTEGER NULL,
IsOnSite BOOLEAN NOT NULL
);
CREATE TABLE SubTask
This is just to confirm that 8.2 beta3 fixes that problem.
Thanks again,
Jean-Pierre Pelletier
From: Tom Lane <[EMAIL PROTECTED]>
To: "JEAN-PIERRE PELLETIER" <[EMAIL PROTECTED]>
CC: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] ERROR: failed to build any 4-way j
ct 1 as col) t3
on t1.col = t3.col
and t2.col = t3.col
and 1 = t3.col
left outer join (select 1 as col) t4
on t3.col = t4.col
I am on PostgreSQL 8.2 beta1 under Windows XP Service Pack 2.
Thanks,
Jean-Pierre Pelletier
e-djuster
It's not clear to me why "not exists" and "not in" return a different result
but it must be per SQL spec
as all DBMS I have seen do that (Oracle, SQL Server, MYSQL, ...)
In most queries I have seen column1 is NOT NULL so IN or EXISTS can both be
u
ement)".
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, October 25, 2005 4:34 PM
Subject: Re: [BUGS] RIGHT JOIN is only supported with merge-joinable join
conditions, PostgreSQL 8.1
le2;
-- Now that we have Row constructor, I can get rid of
my function udftable1row() and this works ok
select
udf(t1)
from
(select (cast(row(1,2) as table1)).*) t1
cross join table2;
I am on PostgreSQL 8.1 beta3 under Windows XP Service Pack 2.
Thanks,
Jean-Pierre
t1id
and table1.extension in (table2.original, table2.replacement)
left outer join table3
on table2.t3id = table3.t3id
and table1.extension in (table2.replacement);
I am on PostgreSQL 8.1 beta3 under Windows XP Service Pack 2.
Thanks
Jean-Pierre Pelletier
ce Pack 2 with JDBC3 8.1 Build
402.
It worked fine with PostgreSQL 8.1
beta2 and with 8.0.*
Thanks,
Jean-Pierre Pelletier
e-djuster
The antivirus is CA eTrust EZ v 7.0.6.7.
I cannot put back the antivirus on that server
because it is now in production mode.
Jean-Pierre Pelletier
- Original Message -
From: "Qingqing Zhou" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 07, 2005 3:08 PM
Subject: Re:
being restarted many times
every day.
Any idea what might be causing that?
Jean-Pierre Pelletier
- Original Message -
From: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>
To: "Qingqing Zhou" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, October 05, 2005 2:58 PM
S
ent without the server crashing.
After two days, if I haven't seen any of these
error messages there is a very high chance that it's
been fixed by turning off the antivirus.
Jean-Pierre Pelletier
- Original Message -
From: "Qingqing Zhou" <[EMAIL PROTECTED]>
To
inserts but no bulk inserts, the biggest load would come
from
select statements.
Jean-Pierre Pelletier
- Original Message -
From: "Qingqing Zhou" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 05, 2005 3:03 AM
Subject: Re: [BUGS] Possibly corrupted shared memory,
backup but created from
.sql scripts for DDL, and data from user tables were reloaded
from files with "copy from".
We are using Windows 2000 Server, Service Pack 4.
Thanks,
Jean-Pierre Pelletier
e-djuster
---(end of broadcast)---
TIP
we weren't using
it back then.
We are using Windows 2000 Server, Service Pack 4.
Thanks
Jean-Pierre Pelletier
e-djuster
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail co
We were running 7.4 under Cygwin with Windows 2000 Service Pack 4.
- Original Message -
From: "Jim C. Nasby" <[EMAIL PROTECTED]>
To: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, October 03, 2005 6:00 PM
Subject: Re: [BUGS] Unreliabl
we weren't using
it back then.
We are using Windows 2000 Server, Service Pack 4.
Thanks
Jean-Pierre Pelletier
e-djuster
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan
The following bug has been logged online:
Bug reference: 1585
Logged by: Jean-Pierre Pelletier
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Windows 2000 Server, Service Pack 4
Description:could not read from statistics collector pipe
We are running PostgreSQL 8.0.1 since last week and
have thesemessages in our PostgreSQL log file:
2005-02-10 10:27:19 FATAL: could not read
block 38 of relation 1663/17269/16676: Invalid argument
2005-02-10 10:27:19 FATAL: could not read
block 46 of relation 1663/17269/16676: Invalid arg
We are running PostgreSQL 8.0.1 since last week and
have thesemessages in our PostgreSQL log file:
The first time we get the error approx 1/2
hour after restarting PostgreSQL, it is:
FATAL: could not read from statistics
collector pipe: No such file or directory
LOG: statistics collecto
21 matches
Mail list logo
