Re: Postgres 8.3 archive_command - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Postgres 8.3 archive_command
Date
Msg-id 1195725068.4246.147.camel@ebony.site
Whole thread Raw
In response to Re: Postgres 8.3 archive_command  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
Responses Re: Postgres 8.3 archive_command  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2007-11-22 at 10:34 +0100, Zeugswetter Andreas ADI SD wrote:
> > I don't think that should even be a TODO item --- it seems far more
> > likely to provide a foot-gun than useful capability.
> 
> On further reflection I think that initdb time is probably sufficient.
> Do you think that would be a reasonable TODO ?

I think you'd have to explain why this was needed. It was useful for
performance once, but not anymore.

There are many possible errors there, so not a road I would go down
without good reason. Extra configuration is just one more thing to go
wrong and one more thing for people to misconfigure.

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: 8.3devel slower than 8.2 under read-only load
Next
From: "Pavel Stehule"
Date:
Subject: Re: strange bison, cannot remove reduce