Re: insert aborted commands ignored

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Pepe TD Vo <pepevo(at)yahoo(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: insert aborted commands ignored
Date: 2019-01-31 19:28:45
Message-ID: 49E280F0-7021-4FD7-AA99-985A86FA899C@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


> On Jan 31, 2019, at 12:14 PM, Pepe TD Vo <pepevo(at)yahoo(dot)com> wrote:
>
> ERROR:current transaction is aborted, commands ignored until end of transaction block
>
> I see each column has extra E' in front, is that right in postgres? How can I prevent this issue?

The e should not be a problem, it's for "extended" strings, which allow some things that the SQL standard doesn't. But 'E'l130' is not legit; was that a copy/paste error.

And you need to post the FIRST error in the logs, not the last one.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Pepe TD Vo 2019-01-31 19:35:44 Re: insert aborted commands ignored
Previous Message Pepe TD Vo 2019-01-31 19:14:47 insert aborted commands ignored