Search Postgresql Archives

Re: Any hope for more specific error message for "value too long..."?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Any hope for more specific error message for "value too long..."?
From: geoff hoffman <geoff@xxxxxxxx>
Date: Fri, 16 Feb 2018 19:21:28 -0700
Cc: PG-General Mailing List <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <CAD3a31WR8X1TpjR_MoZxuz4S0BO3ZkPAeLoQ9rPxKHG=728eoQ@mail.gmail.com>
References: <CAD3a31WR8X1TpjR_MoZxuz4S0BO3ZkPAeLoQ9rPxKHG=728eoQ@mail.gmail.com>

Dang. +1 for that. 

Not that you hadn’t thought of it, and not that it’s actually a viable solution in a jiffy, but switch that mess to JSONB and your problems are over.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Any hope for more specific error message for "value too long..."?
  - From: Ken Tanzer

Prev by Date: Re: shared_buffers 8GB maximum
Next by Date: Re: Database health check/auditing
Previous by thread: Re: Any hope for more specific error message for "value too long..."?
Next by thread: Join query
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux