| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Alexander Korotkov <akorotkov(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Detecting pointer misalignment (was Re: pgsql: Implementation of subscripting for jsonb) |
| Date: | 2021-02-14 00:42:28 |
| Message-ID: | CAPpHfdv=-DGkaSeXOUi4a7OdDF6ZbYG7OyESSY3gwNG9xWmzxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sun, Feb 14, 2021 at 1:59 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> >> On Fri, Feb 12, 2021 at 8:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> Once this does settle, should we consider back-patching so that it's
> >>> possible to run alignment checks in the back branches too?
>
> >> +1
>
> > Let's make sure we have a clean set of builds and then do that.
>
> The buildfarm seems to be happy --- the active members that haven't
> reported in should be unaffected by this patch, either because their
> compiler versions are too old or because they're not x86 architecture.
> So I went ahead and back-patched, and have adjusted longfin to apply
> the -fsanitize switch in all branches.
Perfect, thank you very much!
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-02-15 00:20:07 | pgsql: ReadNewTransactionId() -> ReadNextTransactionId(). |
| Previous Message | Tom Lane | 2021-02-13 22:59:09 | Re: Detecting pointer misalignment (was Re: pgsql: Implementation of subscripting for jsonb) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2021-02-14 01:29:08 | Re: How to get Relation tuples in C function |
| Previous Message | Ranier Vilela | 2021-02-14 00:33:48 | Re: pg_cryptohash_final possible out-of-bounds access (per Coverity) |