| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | We've been affected by a pg_upgrade bug. What do we do next? |
| Date: | 2014-07-16 14:08:20 |
| Message-ID: | 0683F5F5A5C7FE419A752A034B4A0B9797AF6025@sswchi5pmbx2.peak6.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hey,
We performed an upgrade via pg_upgrade from 9.1 to 9.3 a while back, and I'm almost certain we were bitten by this bug:
http://www.postgresql.org/message-id/20140530121631.GE25431@alap3.anarazel.de
Finding the discussion is nice... but what do we do to fix this? I read through the discussion, and it *seems* we can delete the 0000 file and restart since it's only an 8k file and we haven't gone far enough to wrap into a new 0000 file. Will that actually work, though? Or is it too late, since something has already requested that invalid transaction? What do we do?
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-07-16 14:19:40 | Re: We've been affected by a pg_upgrade bug. What do we do next? |
| Previous Message | Derek Poon | 2014-07-16 09:59:22 | Why would I need to explicitly cast a string literal to text? |