Fred Moyer wrote:
> Your UDMA 33 bus will limit disk reads to 33 Mbytes/sec so there is your
> first bottleneck. Get a 66 mhz PCI ide adapter (Promise is cheap) and that
> will increase your disk speed dramatically.
> Also you won't be able to do much with 128 Mb of ram, put in as much as you
>
Your UDMA 33 bus will limit disk reads to 33 Mbytes/sec so there is your
first bottleneck. Get a 66 mhz PCI ide adapter (Promise is cheap) and that
will increase your disk speed dramatically.
Also you won't be able to do much with 128 Mb of ram, put in as much as you
can. That box is likely 66
Richard Emberson writes:
> Does Postgresql support the use of Direct I/O or Raw I/O?
No. And no one has announced any concrete plans to implement it either.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get of
An earlier post referenced a bunch of Oracle performance pages. One of
them,
http://www.ixora.com.au/notes/direct_io.htm
indicates that on Linux 2.4 kernels one can use Direct I/O (if you DB
supports it).
Does Postgresql support the use of Direct I/O or Raw I/O? Base on
another page
http://ww
MG wrote:
>
> Hi!
>
> I subsrcibed to this list again. :)
> I use the version7.0.3-8 of pgsql from RedHat rpm.
> I have a problem. The "/var/lib/pgsql/data/postmaster.opts" file contains this:
>
> /usr/bin/postmaster
> -p 5432
> -D /var/lib/pgsql/data
> -B 64
> -b /usr/bin/postgres
> -i
> -N 32
Hi!
I subsrcibed to this list again. :)
I use the version7.0.3-8 of pgsql from RedHat rpm.
I have a problem. The "/var/lib/pgsql/data/postmaster.opts" file contains this:
/usr/bin/postmaster
-p 5432
-D /var/lib/pgsql/data
-B 64
-b /usr/bin/postgres
-i
-N 32
If I modify it (for examlpes, -N 16
Nicholay P. Chuprynin writes:
> Resently I had to create and manage the (relatively) large table.
> In the mean time it's about 8 million rows, and surely will grow above
> this size.
> The problem is that queries takes absolutely not acceptable time.
> Database located on average Celeron 400 mac
Hello, All!
Resently I had to create and manage the (relatively) large table.
In the mean time it's about 8 million rows, and surely will grow above
this size.
The problem is that queries takes absolutely not acceptable time.
Database located on average Celeron 400 machine with 128 Mb of RAM and
Is there a shell script (or a call to a function) available to check the
existence of an index before it is dropped?
I'm reloading a set of tables, and I want to drop the index before the
COPY, then recreate it.
_
Herb Blacker
Database Administrator
ReCare, Inc.
[EMAIL PR
