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

From: Chozabu <chozabu(at)gmail(dot)com>
To: Kevin Grittner <kgrittn(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 21:04:46
Message-ID: CANxExK4v2LzFwCkgsusMUat39yZKtErP=Y2QtzqefriasZ7X6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Right - I jumped the gun on this one - seems I was creating the DB *not* as
utf-8 - but setting my client to UTF-8, but after dropping and re-creating
I was asking for UTF-8.
Furthermore - my test system had its lang/locales misconfigured!

So, no bug here, just an inexperienced user being silly! (sorry!)

-Alex "Chozabu <http://chozabu.net/blog>" P-B

On Mon, Jan 11, 2016 at 4:42 PM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:

> 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

Browse pgsql-bugs by date

  From Date Subject
Next Message baso10dev 2016-01-11 22:34:33 BUG #13860: Duplicated primary key
Previous Message Kevin Grittner 2016-01-11 16:42:45 Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long