From: | <mallah(at)trade-india(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Cc: | <nagayasus(at)nttdata(dot)co(dot)jp> |
Subject: | case for lock_timeout |
Date: | 2004-07-01 00:04:45 |
Message-ID: | 3840.220.224.18.68.1088640285.squirrel@mail.trade-india.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
With reference to:
http://archives.postgresql.org/pgsql-hackers/2004-06/msg00935.php
Consider a case
1. wherein a database dump takes 2 hrs to complete.
2. A cron gets fired which drops a certain table and recreates it.
3. A set of frequently requested web pages depends on reading from the table in 2
Since 2 will wait for 1 till it finishes, and 3 will wait for 2 this means those
set of webpages will become inaccessible while the backup is in progress.
Whereas if we have something like a lock_timeout 2 will abort within a limited
time duration automatically and the sys admin could get notified to reschedule
it and this problem can get averted.
I feel lock_timeout it will be a nice feature . Lemme know what would be
the solution of the above problem from existing set of features.
Regds
Mallah.
-----------------------------------------
Over 1,00,000 exporters are waiting for your order! Click below to get
in touch with leading Indian exporters listed in the premier
trade directory Exporters Yellow Pages.
http://www.trade-india.com/dyn/gdh/eyp/
From | Date | Subject | |
---|---|---|---|
Next Message | Otto Blomqvist | 2004-07-01 00:11:13 | pg_dump and pg_restore problems |
Previous Message | wespvp | 2004-06-30 23:23:08 | Re: backups |