Re: [PATCH] Better logging of COPY queries if log_statement='all' - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Better logging of COPY queries if log_statement='all'
Date
Msg-id 26709.1476715953@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Better logging of COPY queries if log_statement='all'  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [PATCH] Better logging of COPY queries if log_statement='all'  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
Re: [PATCH] Better logging of COPY queries if log_statement='all'  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 10/17/2016 09:57 AM, Aleksander Alekseev wrote:
>> Sometimes it's useful to log content of files used in COPY ... TO ... and
>> COPY ... FROM ... queries. Unfortunately PostgreSQL doesn't allow to do
>> it, even if log_statement='all'. Suggested patch fixes this.

> I'm not in favor of this, especially if it's not even optional. 

I'm not either.  It sounds good when you're looking at toy examples,
but not when it means repeating gigabytes of COPY data into the log.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Shay Rojansky
Date:
Subject: Re: macaddr 64 bit (EUI-64) datatype support
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran