Sebastián Baioni wrote:
Thanks for answering.
This is my configuration:
# - Memory -
shared_buffers = 1000# min 16, at least max_connections*2, 8KB
each
#work_mem = 1024# min 64, size in KB
#maintenance_work_mem = 16384# min 1024, size in KB
#max_stack_depth = 2048#
Thanks for answering.
This is my configuration:
# - Memory -
shared_buffers = 1000# min 16, at least max_connections*2, 8KB each
#work_mem = 1024# min 64, size in KB
#maintenance_work_mem = 16384# min 1024, size in KB
#max_stack_depth = 2048# min 100, size in KB
The PC
Rod Taylor <[EMAIL PROTECTED]> writes:
> Rebuilding the indexes or integrity confirmations are probably taking
> most of the time.
> What is your work_mem setting?
maintenance_work_mem is the thing to look at, actually. I concur that
bumping it up might help.
regards, to
Rebuilding the indexes or integrity confirmations are probably taking
most of the time.
What is your work_mem setting?
On 22-Dec-06, at 9:32 AM, Sebastián Baioni wrote:
Hi,
We have a database with one table of 10,000,000 tuples and 4 tables
with 5,000,000 tuples.
While in SQL Server it tak
Hi,
We have a database with one table of 10,000,000 tuples and 4 tables with
5,000,000 tuples.
While in SQL Server it takes 3 minutes to restore this complete database, in
PostgreSQL it takes more than 2 hours.
The Backup takes 6 minutes in SQLServer and 13 minutes (which is not a problem)
We ar
