| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Tatsuki Kadomoto <tatsuki(dot)kadomoto(at)proceranetworks(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed |
| Date: | 2016-08-22 18:07:03 |
| Message-ID: | CACjxUsO4VonSNNF8WoV0SuWodhGLcEir_CRA+Fhy8O9aB-cVmg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 22, 2016 at 3:02 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Mon, Aug 22, 2016 at 4:45 PM, Tatsuki Kadomoto
> <tatsuki(dot)kadomoto(at)proceranetworks(dot)com> wrote:
>> Thanks for suggestion for upgrade. I know that's the way to go, but it's not
>> so easy due to circumstances on my side.
>
> Well, I guess it depends on how much you care about your data.
Right. Make sure that whoever is responsible for this decision
knows that until they upgrade they are running with known bugs
which could render the database unusable without warning. It
should at least be an informed decision so that the decision-maker
can stand behind it and feel as good as possible about
circumstances should that happen.
You might want to keep a copy of the email or memo in which you
point this out, in case anyone's memory gets foggy during such a
crisis.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-08-22 18:40:41 | Re: Unique constraint on field inside composite type. |
| Previous Message | Andy Colson | 2016-08-22 14:03:45 | Re: PG vs ElasticSearch for Logs |