| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fast default stuff versus pg_upgrade |
| Date: | 2018-06-19 17:23:29 |
| Message-ID: | CAH2-Wzk6hE0XXFyhgS_DNtg6EifCzstHSM7c2UgR=6bS-aA=rQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 19, 2018 at 10:12 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I have to admit that I think this feature is scary. I'm not sure that
> it was adequately reviewed and tested, and I'm worried this may not be
> the only problem it causes. But this particular problem, as Andres
> says, doesn't seem like anything we can't fix with acceptable risk.
I agree with both points.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-06-19 17:38:06 | Re: [WIP] [B-Tree] Retail IndexTuple deletion |
| Previous Message | Andres Freund | 2018-06-19 17:23:08 | Re: Excessive CPU usage in StandbyReleaseLocks() |