I gmane.comp.db.postgresql.performance, skrev Christopher Kings-Lynne:
> Is it the dump or the restore that's really slow?
Primarily the dump, it seems to be CPU-bound on the postmaster' process.
No signs on IO-bottleneck when I try to monitor with iostat or vmstat
--
./Jesper Krogh, [EMAIL P
Is it the dump or the restore that's really slow?
Chris
Jesper Krogh wrote:
I have a database that I should migrate from 7.3 -> 7.4.3 but pg_dump |
psql seems to take forever. (Several hours) Is there anything that can I
do to speed it up?
The databse is primary a table with 300.000 records of ab
I have a database that I should migrate from 7.3 -> 7.4.3 but pg_dump |
psql seems to take forever. (Several hours) Is there anything that can I
do to speed it up?
The databse is primary a table with 300.000 records of about 200Kbytes
each. ~ 60 GB.
This is becoming an issue with the daily back
Regarding Raid5 at all, you might want to look at http://www.baarf.com
""Stephane Tessier"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I think with your help guys I'll do it!
>
> I'm working on it!
>
> I'll work on theses issues:
>
> we have space for more ram(we use 2 gigs on p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
G u i d o B a r o s i o wrote:
| The box:
| Linux 2.4.24-ck1
| 8 Intel(R) Xeon(TM) MP CPU 2.80GHz
| 4 gb RAM.
| Postgresql 7.4.2
|
| The problem:
| Short in disk space. (waiting new hard)
|
| The real problem:
| Developers usually write queries involvi
On Thu, Aug 05, 2004 at 08:40:35AM +0200, Pierre-Frédéric Caillaud wrote:
> Apache processes running for 30 minutes ?.
>
> My advice : use frames and Javascript !
My advice: Stay out of frames and Javascript if you can avoid it. The first
is severely outdated technology, and the o
The box:
Linux 2.4.24-ck1
8 Intel(R) Xeon(TM) MP CPU 2.80GHz
4 gb RAM.
Postgresql 7.4.2
The problem:
Short in disk space. (waiting new hard)
The real problem:
Developers usually write queries involving the creation of temporary tables.
The BF question:
Is a good idea to link this tmp tables
I am guessing that Oracle can satisfy Q4 entirely via index access,
whereas Pg has to visit the table as well.
Having said that, a few partial indexes may be worth trying out on
data.num_poste (say 10 or so), this won't help the table access but
could lower the index cost. If you combine this w
Hi,
I 've decreased the sort_mem to 5000 instead of 5.
I recreated ma table using integer and real types instead of
numeric : the result is very improved for the disk space :
schema | relfilenode | table | index| reltuples | size
+-+
