Re: Re: BUG #15503: Bytea type column select failed when the length of the value is more than 512M

From: "lichuancheng(at)highgo(dot)com" <lichuancheng(at)highgo(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Re: BUG #15503: Bytea type column select failed when the length of the value is more than 512M
Date: 2018-11-14 08:04:59
Message-ID: 201811141604590662237@highgo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>Nope. palloc() is able to allocate up to 1GB.

The size of bytea is 512M,but in byteaout() function, it expend to more than 1G.
######
rp = result = palloc(VARSIZE_ANY_EXHDR(vlena) * 2 + 2 + 1);
######

--
lchch

From: Michael Paquier
Date: 2018-11-14 15:57
To: lichuancheng(at)highgo(dot)com; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15503: Bytea type column select failed when the length of the value is more than 512M
On Wed, Nov 14, 2018 at 06:23:21AM +0000, PG Bug reporting form wrote:
> is it a bug?

Nope. palloc() is able to allocate up to 1GB.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-11-14 08:40:22 BUG #15504: pgadmin 4
Previous Message Michael Paquier 2018-11-14 07:57:35 Re: BUG #15503: Bytea type column select failed when the length of the value is more than 512M