Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: chozabu(at)gmail(dot)com
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long
Date: 2016-01-11 16:42:45
Message-ID: CACjxUsOY7aE2Y2Wm4SzCWis3wPs7kba+AiZcR=-a2EZ5gtV7=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 8, 2016 at 4:27 AM, <chozabu(at)gmail(dot)com> wrote:

> Using django to create DB, it looks like when data is entered
> into DB, the String length is checked (unicode) but db_restore
> checks the byte length

There is nothing in PostgreSQL called db_restore. If you meant
the pg_restore utility, you need to provide more detail, like
copy/paste of the command line used and the result. If you meant
something else, you are probably reporting the problem to the wrong
place.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Chozabu 2016-01-11 21:04:46 Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long
Previous Message Michael Paquier 2016-01-10 23:21:23 Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while