Re: [HACKERS] [bug-fix] Cannot select big bytea values (~600MB)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Anna Akenteva <a(dot)akenteva(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] [bug-fix] Cannot select big bytea values (~600MB)
Date: 2018-02-16 16:24:08
Message-ID: 20180216162408.te4gbzfhycjbnsp4@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2018-02-16 09:58:29 -0500, Tom Lane wrote:
> Anna Akenteva <a(dot)akenteva(at)postgrespro(dot)ru> writes:
> > [ widen StringInfoData max length to size_t ]
>
> I find this scary as heck. Have you spent any time looking at the
> side effects? There are probably hundreds of places that expect that
> stringinfos won't get larger than 1GB.

FWIW, I think we're going to have to bite that bullet sooner rather than
later. I do agree it's not going to fix this issue for real, and that
we're not going to backpatch it.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-02-16 16:31:28 Re: master check fails on Windows Server 2008
Previous Message Petr Jelinek 2018-02-16 16:04:33 Re: After an error - pg_replication_slot is dropped