Обсуждение: BUG #15907: JSON Select Issue

The following bug has been logged on the website:

Bug reference:      15907
Logged by:          Nathan Walls
Email address:      nwalls@kyledavidgroup.com
PostgreSQL version: 9.6.11
Operating system:   Windows 10
Description:

I have a table that has a column named 'metadata' of type JSON. When I try
to select metadata as part of a group with other columns, I've found that
metadata has to be the first column selected. Otherwise I'll get an error
saying "Not connected to the server or the connection to the server has been
closed," even though a modal will still inform me the query was executed
successfully with N number of rows affected. For example:
SELECT metadata,kind FROM events; --works just fine
SELECT kind,metadata FROM events; --fails

On Mon, Jul 15, 2019 at 08:17:13PM +0000, PG Bug reporting form wrote:
> I have a table that has a column named 'metadata' of type JSON. When I try
> to select metadata as part of a group with other columns, I've found that
> metadata has to be the first column selected. Otherwise I'll get an error
> saying "Not connected to the server or the connection to the server has been
> closed," even though a modal will still inform me the query was executed
> successfully with N number of rows affected. For example:
> SELECT metadata,kind FROM events; --works just fine
> SELECT kind,metadata FROM events; --fails

It would be surprising if this is a bug.  Do you have a reproducible,
self-contained test case that shows the problem?  Perhaps you have an
issue with your client application?
--
Michael