| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, math(at)sai(dot)msu(dot)ru, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Curious buildfarm failures |
| Date: | 2013-01-15 17:18:22 |
| Message-ID: | 50F58F5E.4050304@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/15/2013 12:07 PM, Andrew Dunstan wrote:
>
> On 01/15/2013 11:57 AM, Tom Lane wrote:
>> Well, it could be quite reproducible, if for example what's happening is
>> that the DROP is failing to wait for the checkpointer at all.
>>
>> Is there a way to enable log_checkpoints during a buildfarm run?
>> It'd be good to get timestamps added to the postmaster log entries, too.
>>
>>
>
>
> Yes, it's very easy. In the config file, do something like:
I had a missing quote. should be:
extra_config =>
{
DEFAULT => [
q(log_line_prefix = '%t [%c:%l] '),
"log_checkpoints = 'true'",
],
},
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Garick Hamlin | 2013-01-15 17:22:53 | Re: [PATCH] COPY .. COMPRESSED |
| Previous Message | Andrew Dunstan | 2013-01-15 17:07:02 | Re: Curious buildfarm failures |