Conflict between JSON_AGG and COPY

Dear all, I've found one case. I don't know this is a bug or I config/query some things wrong. Let I describe it. I have a table with structure and data is: id | username | fullname +-+--- 1 | john | John 2 | anna | Anna 3 | sussi | Sussi 4 | david | David Be

Re: dump/restore problem due to CVE-2018-1058 (9.5.12)

On 04/07/2018 12:27 PM, Rory Campbell-Lange wrote: Hi Following an upgrade to 9.5.12, we cannot restore some of our databases due to a schema qualification issue introduced in the new postgres version of pg_dump. Specifically, the problem line is the addition of : SELECT pg_catalog.set_co

dump/restore problem due to CVE-2018-1058 (9.5.12)

Hi Following an upgrade to 9.5.12, we cannot restore some of our databases due to a schema qualification issue introduced in the new postgres version of pg_dump. Specifically, the problem line is the addition of : SELECT pg_catalog.set_config('search_path', '', false); to the header of the

Re: dealing with lock

Thank you Thomas Regards Thomas Le sam. 7 avr. 2018 à 08:01, Thomas Kellerer a écrit : > Adrian Klaver schrieb am 07.04.2018 um 00:02: > >> Is there a way to identify the list of statements that have to rewrite > the table. > > > > https://www.postgresql.org/docs/10/static/sql-altertable.html >

Re: dealing with lock

Thank you Laurenz! Regards Thomas Le sam. 7 avr. 2018 à 00:02, Adrian Klaver a écrit : > On 04/06/2018 12:09 PM, Thomas Poty wrote: > > Thank you Laurenz ! > > > > > > We will certainly have to change our release management. > > > > Is there a way to identify the list of statements that have to