Re: Bug: Reading from single byte character column type may cause out of bounds memory reads.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Aleksander Alekseev <aleksander(at)timescale(dot)com>, Spyridon Dimitrios Agathos <spyridon(dot)dimitrios(dot)agathos(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bug: Reading from single byte character column type may cause out of bounds memory reads.
Date: 2022-07-13 21:25:02
Message-ID: 2537430.1657747502@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2022-07-13 We 11:11, Tom Lane wrote:
>> I complained about this in [1], but that thread died off before reaching a
>> clear consensus about exactly what to do.
>> [1] https://www.postgresql.org/message-id/flat/2318797.1638558730%40sss.pgh.pa.us

> Looks like the main controversy was about the output format. Make an
> executive decision and pick one.

Done, see other thread.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-07-13 22:23:42 Re: proposal: Allocate work_mem From Pool
Previous Message Tom Lane 2022-07-13 21:24:21 Re: The "char" type versus non-ASCII characters