Milan Hromada ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Too much memory consuming with postmaster
Long Description
Big diffrence in performence between 7.1 and 7.2.1. In 7.2.1 postmaster grows up to
700 MB RAM and more w
Hi!
I don't know if it is a bug or not. What I am
facing is that I can't open a database I created. It's better to explain
you by below scenario:
I have installed the Postgres v7.1 or later.
Then, I changed the initial database cluster to another disk, "/mydb".
Then, I changed "PGDAT
Your name : Mike Coleman
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) :alpha
Operating System (example: Linux 2.0.26 ELF) :Tru64 5.1
PostgreSQL version (example: PostgreSQL-
Janko Richter ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
No index usage for "WHERE a IN ( SELECT ...)"
Long Description
I have created a table "testtab" with an unique indexed (smallint) column "a" and
10.000 records. Wh
Sorry but I'm using 7.2.1 and am seeing the problem :).
It didn't occur on the same machine/libs with 7.1.2.
Regards,
Menno Smits
On Thu, Jul 18, 2002 at 11:00:58PM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I just tried with current CVS and got:
> > $ aspg pg_du