Hi Josh, all,
Thanks for your comments. My 2c worth:
Josh Berkus wrote:
Mr. Reid,
To answer your question, it is a bit hard to say at the moment as the
design schema for our project has only just been started. The draft
versions of the ISO standard that I have seen use an object
There seems to be an optimizer problem in 7.1beta3. The query you can see
below worked fast in 7.0.2 but in 7.1beta3 is rather slow. The problem is
that an 'index scan' has been changed to a 'seq scan'. Details:
CREATE
Kovacs Zoltan writes:
There seems to be an optimizer problem in 7.1beta3. The query you can see
below worked fast in 7.0.2 but in 7.1beta3 is rather slow. The problem is
that an 'index scan' has been changed to a 'seq scan'. Details:
Subquery Scan sd_user_grant (cost=38.68..38.85 rows=1
On Sat, 27 Jan 2001, Peter Eisentraut wrote:
Kovacs Zoltan writes:
There seems to be an optimizer problem in 7.1beta3. The query you can see
below worked fast in 7.0.2 but in 7.1beta3 is rather slow. The problem is
that an 'index scan' has been changed to a 'seq scan'. Details:
Kovacs Zoltan [EMAIL PROTECTED] writes:
There seems to be an optimizer problem in 7.1beta3. The query you can see
below worked fast in 7.0.2 but in 7.1beta3 is rather slow. The problem is
that an 'index scan' has been changed to a 'seq scan'. Details:
This is fixed in current sources: I get
Hello!
I'd like to write a function, that makes some calculations
(perhaps applies another function) on every row of a result set returned
by a SELECT query. I thought writing a WHILE loop would work, but I
couldn't assign the individual rows to a variable. Then, I read about the
FETCH
Try using aggregate functions. Creating your own aggregate function is
fairly easy and can produce the exact results you are looking for. In
case this is not good enough, here is an example of some code I used to
loop through rows in a table in pl/pgsql
CREATE FUNCTION
Hello all,
I am in the midst of taking a development DB into production, but the
performance has not been very good so far.
The DB is a decision based system, that currently has queries against tables
with up to 20million records (3GB table sizes), and at this point about a
25GB DB in total.
Hi,
I have been using PostgreSQL-7.0.0 and have had the problem that, when
searching a btree index that contains large numbers of duplicate keys,
Postgres crashes with a BTP_CHAIN error. Now that I have installed 7.1beta3
the problem has seemingly been fixed. Was this problem actually fixed
Mark Volpe [EMAIL PROTECTED] writes:
I have been using PostgreSQL-7.0.0 and have had the problem that, when
searching a btree index that contains large numbers of duplicate keys,
Postgres crashes with a BTP_CHAIN error. Now that I have installed 7.1beta3
the problem has seemingly been fixed.
Tom Lane wrote:
Mark Volpe [EMAIL PROTECTED] writes:
I have been using PostgreSQL-7.0.0 and have had the problem that, when
searching a btree index that contains large numbers of duplicate keys,
Postgres crashes with a BTP_CHAIN error. Now that I have installed 7.1beta3
the problem has
John,
Thanks for your comments. My 2c worth:
That was at least $1.50 worth. Teach me to speak 'off the
cuff' on this list ...
As
far as the
relationship between the schemas for financial and
spatial information
systems goes, a book I have (on OO database management)
goes so far as
Hi again,
Josh Berkus wrote:
John,
Thanks for your comments. My 2c worth:
That was at least $1.50 worth. Teach me to speak 'off the
cuff' on this list ...
Just because I went out and brought a stack of books doesn't mean that I
actually know anything ;-)
As
far as the
13 matches
Mail list logo
