= 2500
vacuum_cost_delay = 10
checkpoint_segments = 256
So, my question for you is: Why does this happen, and what can I do about it?
Regards,
Vegard Bønes
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http
ly an option for the database in question, as it needs to be
accessitble 24 hours a day.
Is there any other possible solution to this?
As a side note, I have noticed that loading times seem to have stabilized
at just above an hour.
Regards,
Vegard Bønes
--
Sent via pgsql-performan
work once it is completed. Is there any point in trying to
use CLUSTER instead if this does not give any result?
Regards,
Vegard Bønes
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
