sing index scan in "query often, update
rarely" environment
On Fri, Oct 07, 2005 at 11:24:05AM +0200, Cestmir Hybl wrote:
Isn't it possible (and reasonable) for these environments to keep track
of
whether there is a transaction in progress with update to given table and
if not
count() queries in environment with infrequent updates.
Cestmir
- Original Message -
From:
hubert depesz
lubaczewski
To: Cestmir Hybl
Cc: pgsql-performance@postgresql.org
Sent: Friday, October 07, 2005 11:54
AM
Subject: Re: [PERFORM] count(*) using
index
alue (count(*)) to perform this kind of query?
(sorry for disturbing if this was already
discussed)
Regards,
Cestmir Hybl
> Looks like he's using the default postgresql.conf settings in which case
> I'm not suprised at pg looking so slow.
The question also is, IMHO, why the hell, postgreSQL still comes out of the
box with so stupid configuration defaults, totally underestimated for todays
average hardware configurati
First of all, thanks for all your suggestions.
They were of two classes:
1. use different data representation (special constant from column domain
instead of NULL)
This is possible, of course, but it makes data model less portable and
requires changes in database abstraction layer of application
Are you seeing this question as totally off-topic in this list, or there is
really no one who knows something about indexing "is null" bits in postgres?
Regards
CH
> Hi,
>
> suppose, for simplicity, there is a table with index like this:
>
> create table TABLE1 (
> A integer
> );
> create inde
Hi,
suppose, for simplicity, there is a table with index like this:
create table TABLE1 (
A integer
);
create index TABLE1_A on TABLE1 (A);
My question is: why psql (7.3.3) does not use index when filtering by A IS
NULL, A IS NOT
NULL expressions?
In fact, I need to filter by expression ((A i
