| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Better logging of COPY queries if log_statement='all' |
| Date: | 2016-10-17 14:52:33 |
| Message-ID: | 26709.1476715953@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-10-17 15:02:31 | Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran |
| Previous Message | Shay Rojansky | 2016-10-17 14:51:15 | Re: macaddr 64 bit (EUI-64) datatype support |