Re: "Not safe to send CSV data" message

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: "Not safe to send CSV data" message
Date: 2009-11-19 03:50:21
Message-ID: 4B04C07D.3030907@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> In any case
> there will certainly always be *some* postmaster messages that could
> be emitted after setting the log_destination GUC and before launching
> the syslogger child. If the designed behavior is that we dump to
> stderr during that interval, we should just do it, without the useless
> and confusing bleating.
>
>
>

I'm fine with that. I don't remember whether I put that in or whether it
came from the original patch author(s). Either way, I assume the reason
was to explain why the message appeared on stderr rather than the
CSVlog. Now we have a couple of years of experience with CSVlog I agree
it's not needed (if it were we'd probably have had more complaints like
yours anyway).

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Chernow 2009-11-19 04:03:28 Re: Listen / Notify - what to do when the queue is full
Previous Message Tom Lane 2009-11-19 03:43:58 Re: Listen / Notify - what to do when the queue is full