I see. Thanks for the quick responses!
On Wed, Jul 19, 2017 at 11:32 PM, Tom Lane wrote:
> Matthew Byrne writes:
> > Would a more feasible approach be to introduce new types (say, TEXT2 and
> > JSONB2 - or something better-sounding) which are the same as the old ones
> >
arrays to the implementations of those types and keep backward
compatibility by leaving TEXT and JSONB alone.
Matt
On Wed, Jul 19, 2017 at 7:30 PM, Tom Lane wrote:
> Matthew Byrne writes:
> > Are there any plans to support \u in JSONB and, relatedly, UTF code
> > point 0
Are there any plans to support \u in JSONB and, relatedly, UTF code
point 0 in TEXT? To the best of my knowledge \u is valid in JSON and
code point 0 is valid in UTF-8 but Postgres rejects both, which severely
limits its usefulness in many cases.
I am currently working around the issue by
I have a large database full of irreplaceable data, and due to a
ridiculous happenstance I accidentally executed this code (as a superuser,
of course):
DELETE FROM pg_catalog.pg_type;
Now the database is *seriously* unhappy - every SQL command returns an
error message. How do I get at my data?
