I will simplify the things in order to describe when the error occurred:
The input of the application is some data which is read from files on disk,
processed and then inserted in the database in one transaction. This total
quantity of data represents an integer number of data files, n*q, where
Hi,
What is the optimization algorithm implemented in postgres 8.2.3 ?
Is it the original System-R optimization or any enhancements have been
implemented ?
Or is it completely new approach?
With Regards,
Bellur Ashwin
Send a FREE SMS to your friend's mobile from Yahoo! Messenger. Get
Sorin N. Ciolofan [EMAIL PROTECTED] writes:
I will simplify the things in order to describe when the error occurred:
The input of the application is some data which is read from files on disk,
processed and then inserted in the database in one transaction. This total
quantity of data
Hello,
I have a data file dumped from a pgsql database version 7.1.2. I am
having troubles restoring this data to a new database server version
8.1.5. Are there some gotcha's involved, did the format change, or some
such?
I have used the createdb command to make the basic database. it's when
Brooks, Jason wrote:
Hello,
I have a data file dumped from a pgsql database version 7.1.2. I am
having troubles restoring this data to a new database server version
8.1.5. Are there some gotcha's involved, did the format change, or some
such?
If you still have the 7.1.2 database use the
Brooks, Jason [EMAIL PROTECTED] writes:
The original file was created with pg_dump -cou.
One thing that's probably biting you is that 8.1 defaults to WITHOUT
OIDS, which is not an option 7.1 pg_dump even knows exists, so it's
not going to say WITH OIDS in the create commands, and then the
COPY
Hi,
I've got PG 8.2.3 running on a dual-core P4, and I noticed that, at least
during reindexing, postgreSQL REINDEX process is using only 1 of those 2 cores.
You can clearly see this from this snippet from top:
Cpu0 : 93.3% us, 6.7% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Cpu1
Hi,
A perfectly normal and healthy PG 8.2.3 instance I have started acting funny -
a query that normally takes only a few milliseconds sometimes runs for minutes.
I thought maybe something's funny with indices, so I reindexed them all.
Didn't help. Thought maybe something's funky with the