| From: | Jeff Frost <jeff(at)pgexperts(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "Wood, Dan" <hexpert(at)amazon(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Old row version in hot chain become visible after a freeze |
| Date: | 2017-09-07 04:45:45 |
| Message-ID: | 15936472-A918-4353-B4BB-B59E0B573490@pgexperts.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Sep 6, 2017, at 8:23 PM, Jeff Frost <jeff(at)pgexperts(dot)com> wrote:
>
>
> Any idea on how to identify affected rows on a running system?
I guess better questions would be:
Is it as simple as:
SELECT id, count(*) FROM foo GROUP BY id HAVING count(*) > 1;
Maybe also need to:
set enable_indexscan = 0;
set enable_indexonlyscan = 0;
before running the SELECT?
Is it possible to affect a DELETE or does it need to be a HOT updated row?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vinod.t.v | 2017-09-07 04:59:10 | BUG #14802: Installation failed for french password Télécharger |
| Previous Message | Kyotaro HORIGUCHI | 2017-09-07 03:33:47 | Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)? |