Re: [HACKERS] Re: [COMMITTERS] pgsql: Permit dump/reload ofnot-too-large >1GB tuples

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: [HACKERS] Re: [COMMITTERS] pgsql: Permit dump/reload ofnot-too-large >1GB tuples
Дата
Msg-id 20161209145147.d5m4bo7b2b2gy5cl@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Permit dump/reload of not-too-large >1GB tuples  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> > > Permit dump/reload of not-too-large >1GB tuples
> > 
> > I apologize for not having paid close enough attention earlier, but:
> > this patch is absolutely unacceptable for the back branches and MUST
> > be reverted there.  Adding another field to StringInfoData is an ABI
> > change that will certainly break large numbers of extensions.  We
> > can't expect those to get recompiled for minor releases.
> 
> Oh, I see the problem now -- it can (and frequently is) stack allocated,
> not just palloc'ed using the StringInfo api, and changing the size
> breaks that.  Rats.  I'll revert tomorrow.

Done.

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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] pg_dump / copy bugs with "big lines" ?
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] tzdata 2016j