POSTGRESQL BUG REPORT TEMPLATE
Your name : Dima Tkach
Your email address : [EMAIL PROTE
Ok, this sit around for a while, and, because there was no responses, I assume, that
nothing jumps out
at you as being terribly with my logic...
Here is the patch (see the original problem description in the bottom)... It seems to
be working (at least that query,
that used to be running out of m
Tom Lane wrote:
>Dmitry Tkach <[EMAIL PROTECTED]> writes:
>
>>*** nodeIndexscan.c.origFri Apr 19 10:29:57 2002
>>--- nodeIndexscan.c Fri Apr 19 10:30:00 2002
>>***
>>*** 505,510
>>--- 505,514
>>
'group by' must be your problem.
If you remove that clause from your second query, you should then get
the same result (77) sum'ing the temp table...
I hope, it helps...
Dima
Marco Kienzle wrote:
>The following problem occur using the sum() function (see the attached
>file for all the details
Did you vacuum it?
I hope, it helps...
Dima
[EMAIL PROTECTED] wrote:
>Markus Grill ([EMAIL PROTECTED]) reports a bug with a severity of 2
>The lower the number the more severe it is.
>
>Short Description
>creating indices after data insertion
>
>Long Description
>Hello,
>
>in my opinion there i
ist) :-(
Perhaps, somebody, familiar with this code could come up with a patch
for this problem?
This would be really great!
Dima
>
>
>Jie Liang
>
>-Original Message-
>From: Dmitry Tkach [mailto:[EMAIL PROTECTED]]
>Sent: Friday, July 12, 2002 7:34 AM
>To: Jie Liang
The attached patch fixes 'Bad Timestamp format' exception when timestamp value is
'ininity' or '-ininity'.
I hope, it helps...
Dima.
Index: AbstractJdbc1ResultSet.java
===
RCS file:
/projects/cvsroot/pgsql/src/interfaces/jdbc/org/
Here is a trouble I am having, that looks like a bug to me:
create table abc (a int, b int, c int);
create index abc_idx on abc (a,b,c);
set enable_seqscan=off;
explain select * from abc where a in (1,2,3);
QUERY
PLAN
Hi, everybody!
I have run into a couple of problems having to do with parsing text
arrays in jdbc (Array.getArray ()):
- First of all, it skips backslashes, but does not really use them as
escape characters
(for example, if the array element has a string, looking like \"blah\",
it will (incorr
Don't you have old jdbc drivers in the classpath by any chance?
Dima
Jeffrey Babb wrote:
Hello,
I am trying to install PostgreSQL 7.3.3 from source on Mac OS X and
having some difficulty.
My configure command is as follows:
./configure --enable-multibyte --enable-unicode --enable-odbc
--w
I am experiencing database server crashes quite frequently (sometimes,
*daily*), and I am having hard time identifying what could possibly be
causing them :-(
They seem to be happenning kinda randomly, I was unable to attribute
them to any specific database activity going on at the time...
The p
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
I am experiencing database server crashes quite frequently
2003-06-10 13:53:32 [14551] FATAL 1: LWLockAcquire: can't wait without
a PROC structure
This is 7.2.1 - I know, I need to upgrade.
Yes, you do.
Makes sense. Thanks!
One more thing to clarify - when you said it was fixed in .3 and .4 did
you mean 7.3 or 7.2.3?
Thanks!
Dima
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
2003-06-10 13:53:32 [14551] FATAL 1: LWLockAcquire: can't wait without
a PRO
You must have some environment setting (like LD_LIBRARY_PATH?) in your
.login or .bashrc (or whatever shell you are using), that tells psql
where to find that library. When you run it via cron, that environment
isn't being set and causes it to fail.
I hope, it helps...
Dima
Serge Obeuf wrot
I am not sure if this is really a bug, but it certainly looks like one
to me...
I have a table that looks something like this:
create table huge_table
(
int x,
int y
);
create index huge_table_idx on huge_table (x,y);
It contains about 80 million rows...
I am trying to get those rows that
... and here is another bug I ran into while trying to investigate my
earlier problem with views a little more:
testdb=# drop rule skip_test;
ERROR: parser: parse error at or near ";" at character 20
testdb=# \h drop rule
Command: DROP RULE
Description: remove a rewrite rule
Syntax:
DROP RUL
Here is a problem a ran into:
testdb=# create table test (x int);
CREATE TABLE
testdb=# create table test_view as select * from test;
SELECT
testdb=# create rule insert_test as on insert to test_view do instead
insert into test values (new.*);
CREATE RULE
testdb=# create rule skip_test as on inse
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
testdb=# create table test_view as select * from test;
SELECT
That is not a view, it's only a static copy of the original table.
regards, tom lane
I know... That was a typo in my sql :-)
But for this example it doe
Tom Lane wrote:
Oh, I see what you're on about. Sorry, a "DO INSTEAD NOTHING" only
suppresses the original command, it does not suppress other rules.
I think what you want is to make the insert_test rule conditional
on x being not null.
Yeah... that's what I was afraid of :-(
The problem is
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
The problem is that in the 'real life' situation the condition is a lot
more complicated than this simple is null test... I hate having to
duplicate it, and I hate even more having to evaluate it twice on every
ins
Oh, I see what you're on about. Sorry, a "DO INSTEAD NOTHING" only
suppresses the original command, it does not suppress other rules.
I think what you want is to make the insert_test rule conditional
on x being not null.
regards, tom lane
Ok... What's wrong with this one then (three rules
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
Ok... What's wrong with this one then
testdb=# insert into test values (null, null);
ERROR: ExecInsert: Fail to add null value in not null attribute x
Try inserting into test_view ...
regards, tom lane
lues (null, null);
It looks like the UNION in the 'not null' rule is the problem.
If I change it to just insert ... select (without the union), or to two
inserts, then it works.
But union always fails, even if I add a 'where false' to the end, so
that it only returns one
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
create rule insert_test as on insert to test_view where new.x is not
null and new.y is not null do instead
(
insert into test
select new.* union
select new.*;
);
Mmm. In CVS tip that throws
ERROR: UNION/INTERSECT/
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
Something like
insert into test
select null,null union select 1,2 where false
has the same problem... and it doesn't refer to any relations.
But that's parsed as
insert into test
(select null,null) union (select 1,2
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
Sure, but it is inside the rule that has 'where x is not null and y is
not null' on it as a qualifier, so
with my test example it should just never get executed in the first place.
You're confusing rules with
Tom Lane wrote:
Dmitry Tkach <[EMAIL PROTECTED]> writes:
It would have saved a lot of trouble if it just complained about that
union thing right away and refuse to create the rule...
That's what happens in CVS tip.
I thought you said it was only complaining about references
Yep ... looks like it got broken in 7.3.
7.2.4 works fine, but 7.3 (and CVS tip) doesn't.
This is because in 7.2, timestamp_date () and timestamptz_date () do the
same thing -
convert the time to Julian date and then subtruct the offset for Y2K,
and both work.
In 7.3 (and 7.4) timestamptz_date (
Thanks a lot for the reply!
The applications uses the jdbc driver with autocommit turned off,
commit and rollback. Do you know if the jdbc driver just starts
a new transaction as soon as the last one was ended with commit/
rollback ?
Yes, it does.
You have to explictly setAutocommit(true) in
Hi, everybody!
I am getting some weird behaviour trying to use a partial index in 7.3:
testdb=# create table a (x int, y int, z int);
CREATE
testdb=# create index a_idx on a(x,y) where z is null;
CREATE
testdb=# create index b_idx on a (x,y);
CREATE
testdb=# explain select * from a where x=1 and
30 matches
Mail list logo
