Re: We've been affected by a pg_upgrade bug. What do we do next?

From: Shaun Thomas <sthomas(at)optionshouse(dot)com>
To: 'Alvaro Herrera' <alvherre(at)2ndquadrant(dot)com>
Cc: 'Andres Freund' <andres(at)2ndquadrant(dot)com>, 'Adrian Klaver' <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?
Date: 2014-07-16 15:30:45
Message-ID: 0683F5F5A5C7FE419A752A034B4A0B9797AF6677@sswchi5pmbx2.peak6.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> BTW if you do a hexdump of the 0000 file, it should be all zeroes.

Yep, that's what I get. :)

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jlliu 2014-07-16 19:05:28 Why pg_toast table not get auto vacuumed?
Previous Message Alvaro Herrera 2014-07-16 15:30:36 Re: We've been affected by a pg_upgrade bug. What do we do next?