| From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Oleg <serovOv(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4688: Bug in cache. |
| Date: | 2009-03-03 15:50:21 |
| Message-ID: | 1d4e0c10903030750t271b0402gce888b08704f1fae@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Mar 3, 2009 at 4:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> I believe the command has been like that for a long time, and this is
>> the first time someone managed to shoot one's foot.
>
> True. Maybe it's not worth the trouble.
IMHO, the consequences are far from being negligible and can put a
cluster down for quite a long time if the database is large
(considering the method suggested by Heikki to fix the problem). So if
we can avoid this sort of problem in a few cases without too much
work, it seems like something we should fix.
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-03-03 15:50:40 | Re: BUG #4688: Bug in cache. |
| Previous Message | Tom Lane | 2009-03-03 15:37:43 | Re: BUG #4688: Bug in cache. |