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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
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 17:25:29
Message-ID: 20180216172529.aqa7huj46fusqceq@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

See these commits:
fa2fa9955280 42f50cb8fa98 b66adb7b0c83
and the discussion threads linked in the commit messages.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Anna Akenteva 2018-02-16 19:00:04 Re: [HACKERS] [bug-fix] Cannot select big bytea values (~600MB)
Previous Message Tom Lane 2018-02-16 16:41:33 Re: [HACKERS] [bug-fix] Cannot select big bytea values (~600MB)