From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Анна Крханбарова <annkpx(at)yandex-team(dot)ru>, Dmitriy Sarafannikov <dsarafan(at)yandex-team(dot)ru> |
Subject: | Re: Logging corruption error codes |
Date: | 2019-06-26 01:59:57 |
Message-ID: | 20190626015925.GC1714@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Jun 25, 2019 at 03:01:23PM +0500, Andrey Borodin wrote:
> Ok, if it's not a bug, should I re-send it to pgsql-hackers@ ? Or
> just register on CF as a new thing...
If you wish to discard this patch and begin a more advanced discussion
about those errors, a new discussion on -hackers would be adapted.
Now, based on what I see you are suggesting for the couple of code
paths related to indexes, I don't see any problem in just applying
what you have (I'd need a second-look at it obviously), in which case
this thread is fine IMO. I don't think that this should be
back-patched though as this is no bug fix, as mentioned upthread.
>> Note: the indentation of the patch is incorrect everywhere. A
>> committer applying your patch would apply pgindent anyway. :)
>
> Oh, sorry. I'm trying to write "like a code around", but do not
> understand clearly how pgindent formats...
No problem. Trying to make the code consistent with the surroundings
is a good habit.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-06-26 02:01:25 | Re: Bug |
Previous Message | Michael Paquier | 2019-06-26 01:48:03 | Re: BUG #15789: libpq compilation with OpenSSL 1.1.1b fails on Windows with Visual Studio 2017 |