| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, "maxim(dot)boguk" <maxim(dot)boguk(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #10675: alter database set tablespace and unlogged table |
| Date: | 2014-10-16 09:56:46 |
| Message-ID: | CA+U5nM+WFWQhaB_3h4Yrkq8Je0Pc9hb6Uq4j1SVBJa=BAe-o9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 16 October 2014 10:00, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> The bug lies in the default behaviour, which we must fix.
>
> But the bug is unrelated to manual checkpoints. So I don't think this is
> really related.
Yes, agreed; I was just thinking that myself.
We need to decouple the bug fix from any behaviour change of the
CHECKPOINT command, so v3 is not the right thing for backpatching.
We may choose to do v3 for later releases, but there does seem to be a
case to retain the current behaviour in some form as well.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sunxin | 2014-10-16 09:58:37 | BUG #11678: database age |
| Previous Message | Andres Freund | 2014-10-16 09:00:45 | Re: BUG #10675: alter database set tablespace and unlogged table |