Re: PostgreSQL a slow DB?

From: <me(at)alternize(dot)com>
To: <operationsengineer1(at)yahoo(dot)com>, <pgsql-novice(at)postgresql(dot)org>
Subject: Re: PostgreSQL a slow DB?
Date: 2006-04-11 00:55:10
Message-ID: 09ef01c65d02$a6540600$0201a8c0@iwing
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

>> 3... switzerland's largest cinema website moved from
>> sql server to
>> postgresql two months ago. lost some comfort
>> (automated backups, jobs) but
>> gained lot of performance, stability... and last but
>> not least, budget! ;-)
>
> Thomas, can't pgsql backups be autmoated via cron
> jobs? i think it is a bit more complex than point and
> click, but once you know how, it isn't and issue
> anymore.
>
> speaking of knowing how... i'll be asking just this
> question in the future. ;-)

of course it can. but it's not as comfortable as through an internal db
scheduling job. in mssql, you also could schedule just about anything...
like reindex, data integrity checks, etc.. all of these can be handled
through a cron job or a windows task as well, but its kinda an external
process compared to the way it is done in mssql.

i saw internal schedule jobs already being on the wishlist for future pgsql
versions :-)

cheers,
thomas

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Alan Hodgson 2006-04-11 01:04:03 Re: PostgreSQL a slow DB?
Previous Message Lan Barnes 2006-04-10 23:53:27 Triggering a table id from a sequence