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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Permit dump/reload of not-too-large >1GB tuples
Date: 2016-12-06 03:10:46
Message-ID: 27737.1480993846@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2016-12-06 03:38:03 Re: [COMMITTERS] pgsql: Permit dump/reload of not-too-large >1GB tuples
Previous Message Andres Freund 2016-12-06 02:20:11 Re: [COMMITTERS] pgsql: Add support for restrictive RLS policies

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-12-06 03:38:03 Re: [COMMITTERS] pgsql: Permit dump/reload of not-too-large >1GB tuples
Previous Message Jim Nasby 2016-12-06 03:10:41 Re: Tackling JsonPath support