First off, thanks to everyone on the list who suggested useful workarounds
to me - and I wanted to start off by saying that with the workarounds my
application is working wonderfully again.
Anyway, here's some more information about the "=" vs. "<= and >=" question
I had earlier today...
On Tu
Ron Mayer <[EMAIL PROTECTED]> writes:
>> I'm particularly interested in the correlation estimate for the dat
>> column. (Would you happen to have an idea whether the data has been
>> inserted more-or-less in dat order?)
> I beleve much of February was loaded first, then we back-filled January,
>
I had an issue where my index was not always used on a very large table.
The issue came down to the data distribution and not pulling in enough of
a random sample to get an accurate estimate ( I think the default max value
was around 3000 sample rows ( 300 * 10 default_samples -- see analyze.c
On Tue, 26 Mar 2002, Tom Lane wrote:
>
> Ron Mayer <[EMAIL PROTECTED]> writes:
> > [...] pretty large, PostgreSQL suddenly stopped using indexes [...]
> [...]
>
> 212K estimate for 180K real is not bad at all. So the problem is in the
> cost models not the initial row count estimation.
>
> If yo
Hi Tom,
thanx for your quick response.
Yes the DB is on a NFS mounted volume, but i have checked my logs: There are no
nfs error messages. As i said these error occures only from time to time (3
times in the last 6 month...I guess).And the only thing i recognized (except
the same errormessage (xl
"Michael Beckstette" <[EMAIL PROTECTED]> writes:
> from time to time my postmaster crashes with the below mentioned errormessage.
> DEBUG: MoveOfflineLogs: remove 000D00A3
> FATAL 2: MoveOfflineLogs: cannot read xlog dir: Invalid argument
Hmm. I cannot see a reason for the xlog direct
Ron Mayer <[EMAIL PROTECTED]> writes:
> Once some of my tables started getting pretty large, PostgreSQL
> suddenly stopped using indexes when I use expressions like "col = value"
> decreasing performance by 20X.
Hmm. The EXPLAIN shows that the planner is not doing too badly at
estimating the n
Hi,
from time to time my postmaster crashes with the below mentioned errormessage.
I am using PostgreSQL 7.1.2 on sparc-sun-solaris2.5.1, compiled by GCC 2.95 on
a 4CPU/4GB UltraSparc II system.
The crash happened during a VACUUM ANALYZE which i perform every 30 minutes.
At the point of the cra
In porting a pretty large (10s of millions of records) data warehouse
from Oracle to PostgreSQL,
Once some of my tables started getting pretty large, PostgreSQL
suddenly stopped using indexes when I use expressions like "col = value"
decreasing performance by 20X. This meant that my daily
Hello,
I am working on Red Hat Linux v7.1 and am
trying to install PostgreSQL7.2 on it.
I am using the rpms directly rather than installing
it from the source code. I see that there are rpm's available for red hat v6.2
and v 7.2. Mine being v 7.1 I chose to use the one for v6.2. However I ha
[EMAIL PROTECTED] writes:
> case sensitivity in pg_dumpall
This is fixed in 7.2.1.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to
Volker Klemann ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
case sensitivity in pg_dumpall
Long Description
Dear people from postgres,
Don't know if I am the first where this bug appeared:
While updating from 7.1.2 to 7.2 I
12 matches
Mail list logo
