Re: BUG #13446: pg_dump fails with large tuples

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: cpt(at)novozymes(dot)com
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13446: pg_dump fails with large tuples
Date: 2015-06-17 04:08:33
Message-ID: CAB7nPqTxBWtcguK89=D7a6GuOLv=-SY-HmQY3Z-z61Rdwh2J0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jun 16, 2015 at 8:20 PM, <cpt(at)novozymes(dot)com> wrote:
> This message then shows up in the server logs. It looks like maybe pg_dump
> is limited to exactly 1GB textual representation?

Yep. That's a known limitation of COPY and palloc() in general.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Xavier 12 2015-06-17 07:20:37 Re: pg_xlog on a hot_stanby slave
Previous Message Michael Paquier 2015-06-17 03:45:16 Re: BUG #13443: master will remove dead rows when hot standby(use slot) disconnect